You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
I recently switched to using the new 0.11.0 version of the VS Code extension tools which includes the new vscode.d.ts installer. Today @andydtoma reported an issue on my repo saying that the install script isn't working from behind a proxy. Here are the contents of his report:
I have cloned the project on a Win7 workstation behind enterprise proxy.
When trying to install the package dependencies with npm install I get ETIMEDOUT:
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\DTOMA\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.2.6
npm ERR! npm v3.7.1
npm ERR! code ELIFECYCLE
npm ERR! PowerShell@0.3.1 postinstall: node ./node_modules/vscode/bin/install
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the PowerShell@0.3.1 postinstall script 'node ./node_modules/vscode/bin/install'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the PowerShell package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node ./node_modules/vscode/bin/install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs PowerShell
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls PowerShell
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\DTOMA\Documents\GitHub\vscode-powershell\npm-debug.log
I have tried with both last versions of node.js v4.2.6 and v5.5.0 with the same result.
Attached the result npm-debug.log: npm-debug.log.txt
The proxy settings in settings.json are fitted to the environment.
On the same system, when I installed the marketplace version of the extension I had to apply the @joaomoreno workaround (Jan 4th) from the vscode issue microsoft/vscode#69
I think there is something similar in the dependency hierarchy.
Do you have any idea why this might be happening?
The text was updated successfully, but these errors were encountered:
Hi guys,
I recently switched to using the new 0.11.0 version of the VS Code extension tools which includes the new vscode.d.ts installer. Today @andydtoma reported an issue on my repo saying that the install script isn't working from behind a proxy. Here are the contents of his report:
I have cloned the project on a Win7 workstation behind enterprise proxy.
When trying to install the package dependencies with npm install I get ETIMEDOUT:
I have tried with both last versions of node.js v4.2.6 and v5.5.0 with the same result.
Attached the result npm-debug.log:
npm-debug.log.txt
The proxy settings in settings.json are fitted to the environment.
On the same system, when I installed the marketplace version of the extension I had to apply the @joaomoreno workaround (Jan 4th) from the vscode issue microsoft/vscode#69
I think there is something similar in the dependency hierarchy.
Do you have any idea why this might be happening?
The text was updated successfully, but these errors were encountered: