anseki / vscode-color

Helper with GUI to generate color codes such as CSS color notations.
MIT License
97 stars 27 forks source link

not woking at all. error [processBridge]: Error: Cannot get NPM #109

Closed Chrisg333 closed 3 years ago

Chrisg333 commented 3 years ago

Steps to Reproduce:

  1. select a color in the text e.h. #ffffff
  2. press Alt +C then p => this is shown [processBridge]: Error: Cannot get NPM Please visit https://github.com/anseki/vscode-color/issues

I am new to VS Code, so I have no idea what NPM means.

Log (All lines): (Click menu of VS Code "Help > Toggle Developer Tools", and click "Console" tab)

log.ts:197   ERR [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat 'c:\Users\Chris\AppData\Roaming\Jumping Bytes\PureSync\.vscode'
log.ts:197   ERR [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat 'm:\MobileMaster\j Projects\FileSync\.vscode'
abstractExtensionService.ts:840 Extension 'ms-vscode.powershell-preview cannot use PROPOSED API (must started out of dev or enabled via --enable-proposed-api)
updateEnableProposedApi @ abstractExtensionService.ts:829
abstractExtensionService.ts:721 [ms-vscode.powershell]: Command `workbench.action.debug.start` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell]: Command `workbench.action.closePanel` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell]: Command `workbench.action.positionPanelLeft` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell]: Command `workbench.action.positionPanelBottom` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell-preview]: Command `workbench.action.debug.start` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell-preview]: Command `workbench.action.closePanel` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell-preview]: Command `workbench.action.positionPanelLeft` appears multiple times in the `commands` section.
abstractExtensionService.ts:721 [ms-vscode.powershell-preview]: Command `workbench.action.positionPanelBottom` appears multiple times in the `commands` section.
abstractExtensionService.ts:717 [ms-vscode.powershell-preview]: Cannot register multiple views with same id `PowerShellCommands`
_logMessageInConsole @ abstractExtensionService.ts:660
console.ts:137 [Extension Host] Git installation not found.
t.log @ console.ts:112
console.ts:137 [Extension Host] [vscode-icons] v11.1.0 activated!
workbench.html:1 A cookie associated with a cross-site resource at https://visualstudio.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
log.ts:191  WARN Settings pattern "workbench.fontAliasing" doesn't match any settings
log.ts:191  WARN Settings pattern "keyboard.*" doesn't match any settings
workbench.html:1 A cookie associated with a cross-site resource at https://bingsettingssearch.trafficmanager.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
log.ts:191  WARN Settings pattern "workbench.fontAliasing" doesn't match any settings
log.ts:191  WARN Settings pattern "keyboard.*" doesn't match any settings
log.ts:191  WARN Settings pattern "workbench.fontAliasing" doesn't match any settings
log.ts:191  WARN Settings pattern "keyboard.*" doesn't match any settings
log.ts:191  WARN Settings pattern "workbench.fontAliasing" doesn't match any settings
log.ts:191  WARN Settings pattern "keyboard.*" doesn't match any settings
log.ts:197   ERR spawn UNKNOWN: Error: spawn UNKNOWN
    at ChildProcess.spawn (internal/child_process.js:394:11)
    at Object.spawn (child_process.js:549:9)
    at k.doApplyUpdate (C:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\code\electron-main\main.js:538:65)
localProcessExtensionHost.ts:257 Extension Host
localProcessExtensionHost.ts:258 Der Befehl "npm" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
console.ts:137 [Extension Host] Start child process...
console.ts:137 [Extension Host] Start initializing module...
t.log @ console.ts:112
console.ts:137 [Extension Host] Node.js@12.14.1
console.ts:137 [Extension Host] Error: Cannot find module 'npm'Require stack:- c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js- c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js- c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\extension.js- c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js- c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-amd.js- c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\bootstrap-fork.js    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:844:17) at Module._load (internal/modules/cjs/loader.js:737:27) at Function.Module._load (electron/js2c/asar.js:769:28) at Function.t._load (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1092:657)  at Function.i._load (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1061:334)  at Function.n._load (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1057:567)  at Module.require (internal/modules/cjs/loader.js:899:19)   at r (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\loader.js:16:346)    at getNpm (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:139:15)    at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:10)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
console.ts:137 [Extension Host] Continue trying to get NPM...
t.log @ console.ts:112
console.ts:137 [Extension Host] Try to get NPM via usage info.
t.log @ console.ts:112
console.ts:137 [Extension Host] Error: Command failed: npm helpDer Befehl "npm" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
    at checkExecSyncError (child_process.js:630:11) at execSync (child_process.js:666:15)   at electron/js2c/asar.js:727:23 at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:152:27 at getNpm (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:161:11)    at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:10)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
console.ts:137 [Extension Host] Try to get NPM via command path.
t.log @ console.ts:112
console.ts:137 [Extension Host] Error: Command failed: where npmINFORMATION: Es konnten keine Dateien mit dem angegebenen
Muster gefunden werden.
    at checkExecSyncError (child_process.js:630:11) at execSync (child_process.js:666:15)   at electron/js2c/asar.js:727:23 at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:172:22 at getNpm (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:184:11)    at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:10)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
console.ts:137 [Extension Host] Try to get NPM in global directory.
t.log @ console.ts:112
console.ts:137 [Extension Host] Error: Command failed: npm root -gDer Befehl "npm" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
    at checkExecSyncError (child_process.js:630:11) at execSync (child_process.js:666:15)   at electron/js2c/asar.js:727:23 at getNpm (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:195:11)    at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:10)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
console.ts:137 [Extension Host] Try to get NPM via node path.
t.log @ console.ts:112
console.ts:137 [Extension Host] Error: Command failed: node -p "process.execPath"Der Befehl "node" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
    at checkExecSyncError (child_process.js:630:11) at execSync (child_process.js:666:15)   at electron/js2c/asar.js:727:23 at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:203:22 at getNpm (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:205:11)    at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:10)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
console.ts:137 [Extension Host] Error: Cannot get NPM   at initModule (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:220:28)    at getHostCmd (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:331:9) at c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34)    at pickConvert (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris\.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24)    at _executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:220) at _.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:701:595)   at m._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:926) at m._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:892:618)   at m._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:891:252)  at m._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:890:6) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:888:136  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1094:104 at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:233:787) at t.PersistentProtocol._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:238:1004)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:235:927  at l.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:801)  at p.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:231:195)  at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:230:547  at Socket.t (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:240:822)   at Socket.emit (events.js:223:5)    at addChunk (_stream_readable.js:309:12)    at readableAddChunk (_stream_readable.js:290:11)    at Socket.Readable.push (_stream_readable.js:224:10)    at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
t.log @ console.ts:112
notificationsAlerts.ts:40 [processBridge]: Error: Cannot get NPM
onDidChangeNotification @ notificationsAlerts.ts:36
localProcessExtensionHost.ts:257 Extension Host
localProcessExtensionHost.ts:258 INFORMATION: Es konnten keine Dateien mit dem angegebenen
Muster gefunden werden.
Der Befehl "npm" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Der Befehl "node" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
anseki commented 3 years ago

Hi @Chrisg333, thank you for the comment. See document for installing the extension. https://github.com/anseki/vscode-color

Chrisg333 commented 3 years ago

I have now installed nodejs 14.5, as the folder C:\Program Files\nodejs did not exist. Really unclear why VSCode did show in the info dialog a nodejs version being installed.

However still not working. The error changed to [processBridge]: Error: spawn UNKNOWN What ever this means?

Please help

anseki commented 3 years ago

Is the version of Node.js really v14.5? (not 14.15?) Also, could you show me current log?

Chrisg333 commented 3 years ago

Thanks a lot for your answer. yes it is 14.15 In the windows control panel it shows version 14.15 But in VSCode -> Info it shows 12.14.1 ????

  1. I installed VSCode x64 on a system where VSCode has not beed installed bfore
  2. I installed nodejs 14.15 x64 So, what is the problem here?

workbench.desktop.main.js:sourcemap:60 [Extension Host] Git installation not found. b @ workbench.desktop.main.js:sourcemap:60 workbench.desktop.main.js:sourcemap:60 [Extension Host] Start child process... workbench.desktop.main.js:sourcemap:60 [Extension Host] Check version of: electron-prebuilt workbench.desktop.main.js:sourcemap:60 [Extension Host] Check version of: comma-separated-values workbench.desktop.main.js:sourcemap:60 [Extension Host] Check version of: js-yaml workbench.desktop.main.js:sourcemap:60 [Extension Host] Check version of: process-bridge workbench.desktop.main.js:sourcemap:60 [Extension Host] Error: spawn UNKNOWN at ChildProcess.spawn (internal/child_process.js:407:11) at spawn (child_process.js:557:9) at c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:471:19 at c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at getHostCmd (c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:365:5) at c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:394:19 at Object.exports.sendRequest (c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\node_modules\process-bridge\process-bridge.js:468:34) at pickConvert (c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:187:15) at exports.pick (c:\Users\Chris.vscode\extensions\anseki.vscode-color-0.4.5\lib\color-helper.js:229:24) at b._executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:86:88517) at b.$executeContributedCommand (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:86:88849) at p._doInvokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:89:10276) at p._invokeHandler (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:89:9968) at p._receiveRequest (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:89:8638) at p._receiveOneMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:89:7440) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:89:5568 at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:1836) at d.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:15515) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:104:29104 at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:1836) at d.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:15515) at t._receiveMessage (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:20765) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:17659 at v.fire (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:55:1836) at u.acceptChunk (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:12880) at c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:63:12228 at Socket.m (c:\Users\Chris\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:104:12375) at Socket.emit (events.js:315:20) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.Readable.push (_stream_readable.js:212:10) at Pipe.onStreamRead (internal/stream_base_commons.js:186:23) b @ workbench.desktop.main.js:sourcemap:60 workbench.desktop.main.js:sourcemap:738 [processBridge]: Error: spawn UNKNOWN onDidChangeNotification @ workbench.desktop.main.js:sourcemap:738

anseki commented 3 years ago

You can ignore the version of the Node.js in VS Code. You have to check another Node.js that was installed by node -v command, not Windows control panel.

Chrisg333 commented 3 years ago

node -v on a windows command line: v14.15.4

anseki commented 3 years ago

That error means that the Node.js and Electron can not be started. E.g. permission, file path, broken file, etc. Is your Node.js available in a process that VS Code will run? That is, the command has to run without problems.

Chrisg333 commented 3 years ago

I uninstalled your extension as it is not working here. Thanks for you help.

anseki commented 3 years ago

Ok :smile: So, could you close this issue?