restore d/d about d HOT 6 CLOSED

@timoxley I believe you need to run npm cache clean, and reinstall kraken or whichever utility that is affected.

It looks that your npm keeps in cache event-emitter as installed from github not npm, which might have happened if at some point if you used any of my modules in pre-release v0.0.0 versions (e.g. old version of es6-map, in package.json it linked event-emitter from github).

This case no longer exists in npm modules I maintain, and I won't bring back any github dependencies to them. Sorry for confusion it made.

I'm closing it, but if for some reason it doesn't solve the issue and you have more details. Let me know.

from d.

I would also call it a bug in npm. It should not rely on versions that are in package.json if package is installed direclty from git repository. It should not be added to cache and treated as npm published dependency in such case.

from d.

@medikoo thanks, cache clean did fix it, how irritating!

from d.

@medikoo perhaps open an issue on npm/npm?

from d.

I just found one directly related: npm/npm#4042 and most likely there are few more

from d.

@medikoo thanks! if I get a chance I'll follow up with a PR, see if we can get this fixed, it's pretty broken behaviour.

from d.