Matthew Broatch

I agree that this level is too clever. It made me think, "Oh, I didn't realize it was that kind of puzzle game", in a bad way.

Haven't tested it yet but what I'm currently thinking of doing is like: ```javascript const cache = new NodeCache() cache.data = JSON.parse(fs.readFileSync('./db/cache-backup.json')) process.on('exit', () => { fs.writeFileSync('./db/cache-backup.json', JSON.stringify(cache.data)) }) ```...

I wouldn't be opposed, but I'm not sure it makes sense without a hard commitment to 2.0, which might not be the wisest move given that every current project uses...

OK, I opened a giant PR that merges my bondage changes into one repo. I know it's a pain haha, but it would be cool to consolidate!

My 2.0 changes have been merged into a 2.0 branch in this repo. I didn't put in the YarnBound wrapper with markup support and the most drastic API changes, though...

Any recent action on this? Are we just waiting for merge conflicts to be fixed?