Closed MikkoPulkkinen closed 3 years ago
Hi @MikkoPulkkinen, thank you for the comment. That seems a bug of NPM. (https://github.com/npm/cli/issues/2137) Try this, then it may be solved: Windows
cd /d %USERPROFILE%\.vscode\extensions\anseki.vscode-color-0.4.5
npm install npm@6.14.11
Others
cd ~/.vscode/extensions/anseki.vscode-color-0.4.5
npm install npm@6.14.11
Thanks, after doing that there's no error anymore. However, the color picker still doesn't show up. Log:
console.ts:137 [Extension Host] Start child process... console.ts:137 [Extension Host] Check version of: electron-prebuilt console.ts:137 [Extension Host] Check version of: comma-separated-values console.ts:137 [Extension Host] Check version of: js-yaml console.ts:137 [Extension Host] Check version of: npm console.ts:137 [Extension Host] Check version of: process-bridge console.ts:137 [Extension Host] Try to send IPC message: 1
it waits here until mouseclick
console.ts:137 [Extension Host] Try to send IPC message: 2 console.ts:137 [Extension Host] Child process disconnected console.ts:137 [Extension Host] Child process exited with code: 0
Oh, there was already an issue about that. "colorHelper.disableGpu": 1 fixed it. Thank you!
:smile:
I do get the same error! Using npm 7.6.0 on Win10 WSL2 - might there be a compatibility issue with npm7 or could it be Windows (WSL) related?
"colorHelper.disableGpu": 1
didn't help and downgrading to npm6 isn't an option for me, either.
Hi @renet, thank you for the comment. Do you mean that the solution (https://github.com/anseki/vscode-color/issues/108#issuecomment-774365209) failed?
I guess I didn't fully read the solution. I just scanned over it and thought your solution was to globally downgrade npm to that particular version. But you suggested to only install it inside your extension's folder.
This should not be the final solution. Wouldn't it be better to update your code to restore compatibility to the latest npm versions?
Thank you!
Of course this is not a solution to the root of the problem. As I said (https://github.com/anseki/vscode-color/issues/108#issuecomment-774365209), the cause of this issue is the bug of NPM. The bug of NPM might be fixed, or I might replace to libnpm, but I think that this extension have already finished its part since VS Code supports internal Color Picker.
node -v
): v14.15.4npm -v
): 7.5.2Steps to Reproduce:
Log (All lines): (Click menu of VS Code "Help > Toggle Developer Tools", and click "Console" tab)