Each time I run a sudo npm update -g I get this. But the file build.js is there.
sudo npm update -g
> node -v && npm -v
Can anyone explain?
Try npm cache clean. It worked for me.
npm cache clean
How is the cache related to this? Does not make sense to me ...
I’m sorry mate; I don’t know why clearing the cache made npm update -g work again.
npm update -g
OK. Can anybody explain? And why does the cache not clear / invalidate itself after certain operations?
@binarykitchen Sometimes (rarely) the cache does get confused and needs to be cleared. Are you still having this issue? Can please try using the latest version of npm (currently 1.3.23) and close this if your specific issue is resolved?
For reasons I cannot explain nor elaborate, I am not having this issue anymore. Closing now.