[BUG][8.4.0][Windows] npm i -g npm@8 fails in GitHub Actions

[AviVahl]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

This issue appears to have started with the release of npm@8.4.0.

https://github.com/wixplosives/file-services/runs/4976059479?check_suite_focus=true
https://github.com/wixplosives/pleb/runs/4973815604?check_suite_focus=true

Happens on every repository where I'm using npm@8 in GitHub Actions.
I realize this can be a (permission?) issue with GitHub Actions containers, but I wouldn't rule out a regression in npm itself.

Expected Behavior

npm i -g npm@8 should pass on Windows in GitHub Actions

Steps To Reproduce

1. In Github Actions
2. With this (super simple) config: https://github.com/wixplosives/file-services/blob/master/.github/workflows/tests.yml
3. Run 'npm i -g npm@8'
4. See error:

2022-01-28T04:02:14.0117198Z npm ERR! code EPERM
2022-01-28T04:02:14.0117959Z npm ERR! syscall rename
2022-01-28T04:02:14.0119521Z npm ERR! path C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@tootallnate
2022-01-28T04:02:14.0121582Z npm ERR! dest C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@tootallnate
2022-01-28T04:02:14.0123300Z npm ERR! errno -4048
2022-01-28T04:02:14.0163074Z npm ERR! Error: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@tootallnate' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@tootallnate'
2022-01-28T04:02:14.0165302Z npm ERR!  [OperationalError: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@tootallnate' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@tootallnate'] {
2022-01-28T04:02:14.0167111Z npm ERR!   cause: [Error: EPERM: operation not permitted, rename 'C:\npm\prefix\node_modules\npm\node_modules\.node-gyp.DELETE\node_modules\@tootallnate' -> 'C:\npm\prefix\node_modules\npm\node_modules\node-gyp\node_modules\@tootallnate'] {
2022-01-28T04:02:14.0167983Z npm ERR!     errno: -4048,
2022-01-28T04:02:14.0168501Z npm ERR!     code: 'EPERM',
2022-01-28T04:02:14.0169020Z npm ERR!     syscall: 'rename',
2022-01-28T04:02:14.0170019Z npm ERR!     path: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\.node-gyp.DELETE\\node_modules\\@tootallnate',
2022-01-28T04:02:14.0171280Z npm ERR!     dest: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\node-gyp\\node_modules\\@tootallnate'
2022-01-28T04:02:14.0174531Z npm ERR!   },
2022-01-28T04:02:14.0175411Z npm ERR!   errno: -4048,
2022-01-28T04:02:14.0176225Z npm ERR!   code: 'EPERM',
2022-01-28T04:02:14.0176835Z npm ERR!   syscall: 'rename',
2022-01-28T04:02:14.0177871Z npm ERR!   path: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\.node-gyp.DELETE\\node_modules\\@tootallnate',
2022-01-28T04:02:14.0179144Z npm ERR!   dest: 'C:\\npm\\prefix\\node_modules\\npm\\node_modules\\node-gyp\\node_modules\\@tootallnate',
2022-01-28T04:02:14.0179809Z npm ERR!   parent: 'npm'
2022-01-28T04:02:14.0180347Z npm ERR! }
2022-01-28T04:02:14.0180781Z npm ERR! 
2022-01-28T04:02:14.0181378Z npm ERR! The operation was rejected by your operating system.
2022-01-28T04:02:14.0182244Z npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
2022-01-28T04:02:14.0182979Z npm ERR! or that you lack permissions to access it.
2022-01-28T04:02:14.0183459Z npm ERR! 
2022-01-28T04:02:14.0184264Z npm ERR! If you believe this might be a permissions issue, please double-check the
2022-01-28T04:02:14.0185116Z npm ERR! permissions of the file and its containing directories, or try running
2022-01-28T04:02:14.0185804Z npm ERR! the command again as root/Administrator.
2022-01-28T04:02:14.0563679Z 
2022-01-28T04:02:14.0565244Z npm ERR! A complete log of this run can be found in:
2022-01-28T04:02:14.0566097Z npm ERR!     C:\npm\cache\_logs\2022-01-28T04_02_14_018Z-debug.log
2022-01-28T04:02:15.2381520Z ##[error]Process completed with exit code 1.

Environment

• npm: 8..4.0
• Node.js: saw it happening in latest 12/14
• OS Name: win32
• System Model Name: container in GitHub Actions
• npm config: <it's CI, so a bit harder to just execute commands>

[AviVahl]

Just to clarify, this worked up until yesterday's release.

[sirber]

8.4.0 is broken for me too, general use on Windows (ntfs). Same node-gyp error. 8.3.x works though.

[aslushnikov]

This is affecting us as well at http://github.com/microsoft/playwright

We'll downgrade to 8.3 for now.