Closed agroszer closed 8 years ago
This is not technically feasible. npm update wipes out the directory before it updates the package. And I think that because you're using git hashes in your package.json, you're short-circuiting npm's ability to do a no-op when the package hasn't changed.
as it looks only npm install checks that, npm update just complains about
PhantomJS not found on PATH
thus subsequent npm update's would download the binary again