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

Erro ao instalar o method-override

Por gentileza ao tentar instalar o method-override (npm install method-override@3.0.0 --save-exact) aparece o seguinte erro:

npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\sshpk-c8d6aa8e\man\man1\sshpk-conv.1' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\sshpk-c8d6aa8e\man\man1\sshpk-sign.1' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\sshpk-c8d6aa8e\man\man1\sshpk-verify.1' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\argument-tag-extra-whitespace\expected.html' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\argument-tag-extra-whitespace\input.htmljs' npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\argument-tag-multiple' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\build\Release.deps\Users\eshanker\Code\fsevents\lib\binding\Release\node-v64-darwin-x64\fse.node.d' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\build\Release\obj.target\action_after_build.stamp' npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\build\Release' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\multiline-html-block-nested\expected.html' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\multiline-html-block-nested\input.htmljs' npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\multiline-html-block' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\needle\bin\needle' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\string-width\index.js' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\string-width\license' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\string-width\package.json' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\string-width\readme.md' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\scriptlet-html-block\expected.html' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest-1.x\scriptlet-html-block\input.htmljs' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest\argument-tag\expected.html' npm WARN tar ENOENT: no such file or directory, open 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest\argument-tag\input.htmljs' npm WARN tar ENOENT: no such file or directory, lstat 'C:\Users\lucas\Documents\Node\node_modules.staging\htmljs-parser-02792a23\test\autotest\attr-comma-multiline' npm WARN node@1.0.0 No repository field. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents): npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename 'C:\Users\lucas\Documents\Node\node_modules.staging\fsevents-8635e614\node_modules\abbrev' -> 'C:\Users\lucas\Documents\Node\node_modules.staging\abbrev-392748b7'

npm ERR! code E404 npm ERR! 404 Not Found: flatmap-stream@0.1.0

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\lucas\AppData\Roaming\npm-cache_logs\2019-02-25T20_41_22_272Z-debug.log

4 respostas

Oi Lucas tudo bem?

Qual versão do node está usando?

Esse monte de texto é o que está no C:\Users\lucas\AppData\Roaming\npm-cache_logs\2019-02-25T20_41_22_272Z-debug.log ?

Se não posta ele também pra gente analisar.

No meu node 6.4.1 instalou certinho. Vou tentar mudar a versão do meu node para ficar igual a sua e ver se tomo o mesmo erro. Aí saberei se é problema de uma versão específica do node ou é algo na infraestura do seu pc.

Oi Andre.

Estou utilizando a versão do Node 10.15.1. Segue o final do conteúdo do log:

1236 verbose cwd C:\Users\lucas\Documents\Node 1237 verbose Windows_NT 10.0.17134 1238 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "method-override@3.0.0" "--save-exact" 1239 verbose node v10.15.1 1240 verbose npm v6.4.1 1241 error code E404 1242 error 404 Not Found: flatmap-stream@0.1.0 1243 verbose exit [ 1, true ]

Obrigado.

Andre mexi em algumas coisas e consegui. Mexi em tantas coisas que não sei o que resolveu rs. De qualquer modo muito obrigado pelo apoio.

Abraços

solução!

Disponha!! Que bom que conseguiu, uma vez tentei instalar o nodemon aí não consegui, aí passou uns dias tentei denovo aí deu certo. Também fiquei sem entender!

Bons estudos!!!