Jinder Sidhu

Also seeing this issue and it appears quite a lot when the collection is updated. Can't seem to figure out exactly what's happening, but I can trigger it consistently if...

@Kim-Andersen thanks for the tip - seems to solve the issue for me!

I've just noticed in our code that the trackBy code was using an incorrect function signature (it was comparing on the first parameter which is index and not the item...

Having the same issue. Removing the initial array fixes it for me too.

Presumably to use it in a browser.... This is a package I've inherited, and it's not actively maintained. I'm really not sure why so many Node-specific packages rely on it....

Although it's not packaged (browserify-style), it does depend on the process and util NPM packages. So there's certainly going to be dependencies that are using it and packaging it themselves....

I'm a bit apprehensive about pulling this from the registry without knowing for sure it won't break anything. I'll deprecate it this weekend and monitor it for a while to...

You certainly can use it without having an absolute/relative path. RequireJS lets you specify the paths in its config for named modules. You're welcome to contact any of the dependent...

I think in those instances, you'd only see the message if they're specifically forcing the use of the package under Node. Really, what we want is to somehow notify users...

Okay, so, latest plan of action: Update the readme to _clearly_ indicate it's not necessary to have a dependency on this module if you're only running on Node. Any objections?...