This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Empty .bin directories are not removed and result in ENOENT errors #10938
Comments
|
Likely related/same as #10887 |
iarna
pushed a commit
that referenced
this issue
Jan 20, 2016
Previously, installed packages that contained node_modules with a .bin directory woudn't get cleaned up correctly. After unbuild of that particular package, npm would complain with ENOENT errors because the package directory would be empty (without package.json), as it only contains the leftover `node_modules/.bin` directory. PR-URL: #11181 Credit: @chrisirhc Reviewed-By: @othiym23 Fixes: #10887 Fixes: #10938
This was referenced Jan 31, 2016
This was referenced Feb 7, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With npm@3 I am regularly getting ENOENT errors.
When doing
npm removeand seemingly also when doingnpm install(perhaps because npm is moving things around in the tree?), I end up with empty.bindirectories like this:Where foobar and everything under it is empty, but the .bin wasn't removed. Any other
npm installthen reports ENOENT fornode_modules/foobar/package.json(as per #10471).Removing all the empty directories fixes it:
Expected behaviour: npm should have removed these directories already.
npm version 3.5.3
Thanks.
The text was updated successfully, but these errors were encountered: