Solucionado (ver solução)
Solucionado
(ver solução)
3
respostas

Problema Proxy Node.js

Provavelmente meu problema é com proxy, Tem um post que passa dois comandos, mas não consegui resolver. Apesar de não usar o Internet Explorer, nele consegui as infos do IP e PORTA do proxy. Abaixo meu log.

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@3.10.10
3 info using node@v6.11.5
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle alurapic@1.0.0~prestart: alurapic@1.0.0
6 silly lifecycle alurapic@1.0.0~prestart: no script for prestart, continuing
7 info lifecycle alurapic@1.0.0~start: alurapic@1.0.0
8 verbose lifecycle alurapic@1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle alurapic@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\p0022402\Desktop\bkpTJ\cursos\angular01\node_modules\.bin;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Common Files\Roxio Shared\10.0\DLLShared\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\Java\jdk1.7.0_45\bin;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files\Aladdin\eToken\PKIClient\x32;C:\Program Files\Aladdin\eToken\PKIClient\x64;C:\Program Files\Git\cmd;C:\Program Files (x86)\Skype\Phone\;C:\Program Files\nodejs\;C:\Users\p0022402\AppData\Roaming\npm
10 verbose lifecycle alurapic@1.0.0~start: CWD: C:\Users\p0022402\Desktop\bkpTJ\cursos\angular01
11 silly lifecycle alurapic@1.0.0~start: Args: [ '/d /s /c', 'node server.js' ]
12 silly lifecycle alurapic@1.0.0~start: Returned: code: 1  signal: null
13 info lifecycle alurapic@1.0.0~start: Failed to exec start script
14 verbose stack Error: alurapic@1.0.0 start: `node server.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid alurapic@1.0.0
16 verbose cwd C:\Users\p0022402\Desktop\bkpTJ\cursos\angular01
17 error Windows_NT 6.1.7601
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 error node v6.11.5
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error alurapic@1.0.0 start: `node server.js`
22 error Exit status 1
23 error Failed at the alurapic@1.0.0 start script 'node server.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the alurapic package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node server.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs alurapic
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls alurapic
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
3 respostas
solução!

É proxy sim, mas há uma solução, aliás, vamos torcer para que seja solução no seu caso. Faça o seguinte no seu prompt, uma única vez:

npm set strict-ssl false

Depois, tente fazer a instalação.

Se o problema continuar, tente configurar o proxy dessa forma:

npm config delete proxy
npm config delete https-proxy

Se por fim, se não funcionar, última opção, que é configurar o proxy:

npm config set proxy http://proxy.company.com:8080
npm config set https-proxy http://proxy.company.com:8080

Nesse caso, tem que usar as configurações de proxy da sua empresa.

Tenha certeza de estar usando Node.js 6 ou superior, de preferência, Node 8.6.

Não sei o que funcionou pois fiz ambos (risos).

1) Antes havia instalado o Node do link downloads. Dessa vez instalei o 8 que tem na página inicial.

2) fiz o comando de deletar o proxy, sugerido neste post.

Fato é que agora no npm start rodou! \o/

Que boa notícia! Agora é continuar com os estudos!

Sucesso e bom estudo Pacheco!