rebridge

I agree it doesn't seem super useful, but it can be used to pull some semantic tricks. I used it in [Rebridge](https://github.com/CapacitorSet/rebridge/) to implement syntactic sugar for database access, so that accessing a property on an object translates transparently to a query, and I've seen it used to [allow for typos in property names](https://github.com/mathiasbynens/tpyo).

It was much more difficult to understand. For whatever reason, it appears that I couldn't `splice` arrays (https://github.com/CapacitorSet/rebridge/issues/2), and I honestly couldn't figure out what was wrong. There was also the issue of error handling, which is much easier with promises.

https://github.com/CapacitorSet/rebridge/blob/master/index.j... A quick review... 1. Could have made your life easier using promises or equivalent to handle the asynchronous flows. 2. Could have made your life easier using lodash instead of implementing recursive functions that can throw stack overflows. 3. JSON.parse can throw with invalid JSON and JSON.stringify can throw with circular references. There might be other cases in which those throw. 4. Line 25: "if key is inspect, return thing". That wasn't in test code, but in the actual library code. That would execute in the application using this library. ...And that part was the one that pushed me over the edge and the extent of my review. I punched my keyboard. Then, you claim it handles a redis connection transparently. But nobody would use a redis server without redundancy, you nee