Multiple copies of the library will cause issues

[swannodette]

Multiple copies of the library will cause issues

[aearly]

Looks like you might have to use a dependency-injection styled strategy if you distribute a library that relies on mori and will return mori collections, or otherwise might have multiple mori versions in your app. For example:

var mori = require("mori");
var myLib = require("my-lib")(mori);

var foo = myLib.getSomeCollection();

console.dir(mori.clj_to_js(foo)); // works because foo is defined using the same verison of mori

[tgriesser]

Yeah, that would definitely be another approach - just gets to be a bit of a hassle if you want to use persistent data structures in a lot of libraries, pretty much everything then turns into that style of module loading.

I just wanted to see if this was fundamentally impossible to work-around with how the library and such are compiled. Thinking about it a bit more, I'm realizing it probably is, but figured I'd check anyway.

[swannodette]

There's nothing to see here, npm doesn't magically solve dependency issues. This will plague any popular data structure library. All workarounds require complications & performance degradations which we're not going to pursue.

[tgriesser]

Sounds good, thanks. Is this worth noting in the docs at all? If so I can open a PR for that.