Uh oh!
There was an error while loading. Please reload this page.
fix: handle ENOTEMPTY errors in moveFile - #8721
Merged
Merged
Conversation
Like EEXIST, we handle ENOTEMPTY when we fail to moveFile. A user reported they consistently could not update our CLI tool. [1] In that report it always had the same file it tried to rename to. I believe what is happening here is when NPM retires an old version it renames it to a deterministic path. However, I suspect a previous update was interrupted leaving a non-empty directory at the destination. When googling ENOTEMPTY all the results seem to be about npm failures with users suggesting clearing out node_modules. Maybe this will also solve those issues. [1]: https://gist.github.com/keegancsmith/5dac339583cc127031da6ed0e8512d47
owlstronaut
approved these changes
Dec 5, 2025
owlstronaut
left a comment
There was a problem hiding this comment.
Good fix for a real user problem. Extending the EEXIST recovery logic to also handle ENOTEMPTY makes sense - both indicate the retirement path already has content from a previous interrupted install. Test coverage looks solid. Thanks!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Like EEXIST, we handle ENOTEMPTY when we fail to moveFile.
A user reported they consistently could not update our CLI tool. 1 In that report it always had the same file it tried to rename to. I believe what is happening here is when NPM retires an old version it renames it to a deterministic path. However, I suspect a previous update was interrupted leaving a non-empty directory at the destination.
When googling ENOTEMPTY all the results seem to be about npm failures with users suggesting clearing out node_modules. Maybe this will also solve those issues.