Description
If https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint is running on a project with eslint-plugin-import-x and eslint-import-resolver-typescript, a lock is established on node_modules\@unrs\resolver-binding-win32-x64-msvc\resolver.win32-x64-msvc.node. Making it so any run that needs to remove this file (npm install after removing/updating these deps, or having to nuke the node_modules) will fail.
The current workaround is to manually disable the ESLint extension + restart the extension host (OR close the editor entirely), then try again.
(powershell error:)
System.UnauthorizedAccessException: Access to the path '...\node_modules\@unrs\resolver-binding-win32-x64-msvc\resolver.win32-x64-msvc.node' is denied.
at Microsoft.PowerShell.Commands.FileSystemProvider.RemoveFileSystemItem(FileSystemInfo fileSystemInfo, Boolean force)
Dprint has a similar issue dprint/dprint-vscode#88 . That issue also mentions a possible workaround. Not sure if it applies here, but since this resolver is called by another plugin, maybe there's something to be done. If not then this is another note to an existing ecosystem-wide issue on Windows (I don't think unix-like systems have that issue).
I'm guessing there's probably nothing actionable in this repo, but that's where the symptoms happen, feel free to move/duplicate/link to the appropriate repository.