Ember.js + IndexedDB integration broken about node-extend

[nolanlawson]

Hey @ljharb, this issue is super old and PouchDB has actually since implemented an aggressive object-cloning logic in order to work around subtle IndexedDB issues, so it's probably not even reproducible anymore. I dunno what the status of Ember is.

I'm happy just to close this issue! :)

[ljharb]

I'd file that on Ember - modifying global prototypes (outside of a spec-compliant shim) is pure insanity, and the instant a lib does it, all bets are off.

Does Ember use node-extend?

[ljharb]

However, if you can provide a PR that doesn't break this functionality but makes it more robust in a crazy irresponsible prototype-modifying world, I'll be happy to merge it in :-)

[nolanlawson]

Yeah, that's exactly what I suspect I don't have the patience to do. :) In any case, yeah, the fault is really on Ember for modifying the prototype (tisk tisk!), although they probably had a good reason for it, since they need some way to observe objects without Object.observe.

[ljharb]

I'm no longer checking for nodeType or setInterval here, so can you give this another try with v2.0.0?

[ljharb]

@nolanlawson ping