[BUG] Unexpected warning on each operation

[zdm]

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

1. I have webpack-dev-server running in the other console.
2. When I am trying to exec any npm command, for example npm update I am getting warnings:

npm WARN logfile Error: EPERM: operation not permitted, unlink 'C:\Users\zdm\.npm-cache\_logs\2021-12-05T06_01_16_787Z-debug-0.log'
npm WARN logfile  error removing log file C:/Users/zdm/.npm-cache/_logs/2021-12-05T06_01_16_787Z-debug-0.log [Error: EPERM: operation not permitted, unlink 'C:\Users\zdm\.npm-cache\_logs\2021-12-05T06_01_16_787Z-debug-0.log'] {
npm WARN logfile   errno: -4048,
npm WARN logfile   code: 'EPERM',
npm WARN logfile   syscall: 'unlink',
npm WARN logfile   path: 'C:\\Users\\zdm\\.npm-cache\\_logs\\2021-12-05T06_01_16_787Z-debug-0.log'
npm WARN logfile }

3. If I close webpack - mentioned log file become unlocked and warnings are not shown.
4. This issue introduced in npm v8.2.0;

Expected Behavior

Don't want to see this warnings.

Steps To Reproduce

Described above

Environment

• npm: 8.2.0
• Node: 17.2.0
• OS: windows 11
• platform: -
• npm config: no npm config

[lukekarrys]

Thanks for the report @zdm! This was due to our new debug log behavior which opens a file descriptor for the debug log at the beginning of the process. We also attempt to clean out old log files, so what ended up happening was we were attempting to close a currently open file which causes that error on Windows. This is actually ok, so the change was just to not bubble up that error to the warn loglevel and instead drop it to the silly level.

This change should go out on Thursday, but let me know if you see any other weird behavior before that.

[zdm]

The problem is that this warnings are mixed with the command output and prevents to read it.