Npm install windows 10 не работает

Установка Npm не работает в Windows 10

У меня проблема с nodejs. Я пытаюсь установить библиотеку ember.js через командную строку. Когда я запускаю команду «npm install», этот журнал появляется:

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 ‘install’ ] 2 info using npm@2.11.3 3 info using node@v0.12.7 4 verbose config Skipping project config: C:\Users\Antonio/.npmrc. (matches userconfig) 5 verbose readDependencies loading dependencies from C:\Users\Antonio\package.json 6 error install Couldn’t read dependencies 7 verbose stack Error: ENOENT, open ‘C:\Users\Antonio\package.json’ 7 verbose stack at Error (native) 8 verbose cwd C:\Users\Antonio 9 error Windows_NT 6.3.9600 10 error argv «C:\Program Files\nodejs\\node.exe» «C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js» «install» 11 error node v0.12.7 12 error npm v2.11.3 13 error path C:\Users\Antonio\package.json 14 error code ENOPACKAGEJSON 15 error errno -4058 16 error package.json ENOENT, open ‘C:\Users\Antonio\package.json’ 16 error package.json This is most likely not a problem with npm itself. 16 error package.json npm can’t find a package.json file in your current directory. 17 verbose exit [ -4058, true ]

Я посетил NPM Troubleshooting, но я не могу найти решение (я попробовал три варианта, но ничего не случилось). Просто сказать: в AppData/Roaming еще есть папка с именем «npm».

Источник

Npm install doesn’t work on Windows 10

i have an issue with nodejs. I’m trying to install ember.js library through the command line. When i launch «npm install» command this log appear:

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 ‘install’ ] 2 info using npm@2.11.3 3 info using node@v0.12.7 4 verbose config Skipping project config: C:\Users\Antonio/.npmrc. (matches userconfig) 5 verbose readDependencies loading dependencies from C:\Users\Antonio\package.json 6 error install Couldn’t read dependencies 7 verbose stack Error: ENOENT, open ‘C:\Users\Antonio\package.json’ 7 verbose stack at Error (native) 8 verbose cwd C:\Users\Antonio 9 error Windows_NT 6.3.9600 10 error argv «C:\Program Files\nodejs\\node.exe» «C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js» «install» 11 error node v0.12.7 12 error npm v2.11.3 13 error path C:\Users\Antonio\package.json 14 error code ENOPACKAGEJSON 15 error errno -4058 16 error package.json ENOENT, open ‘C:\Users\Antonio\package.json’ 16 error package.json This is most likely not a problem with npm itself. 16 error package.json npm can’t find a package.json file in your current directory. 17 verbose exit [ -4058, true ]

I’ve visited NPM Troubleshooting but i can’t found the solution (i tried the three options but nothing happen). Just to say: there is yet a folder named «npm» in AppData/Roaming.

Источник

npm install is not working in Windows 10 #15719

Comments

hemakh commented Feb 9, 2017 •

I have installed nodejs latest on Windows 10 (64-bit) and the PATH is already setup. Now when i am trying to install any npm modules globally using npm install -g

then I am getting the following error:

» npm ERR! node v6.9.5 npm ERR! npm v3.10.10 npm ERR! 1961 == 0 npm ERR! npm ERR! If you need help, you may report this error at: npm ERR! «>

The npm-debug.log shows:

I do not understand the error in windows 10 while installing npm packages. Please let me know if this can be fixed.

The text was updated successfully, but these errors were encountered:

hemakh commented Feb 11, 2017 •

I have cleared the npm cache and after a restart tried again with npm install command.

Error is info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127.0.0.1:80 Can any one help me in fixing this issue?

jpaulin commented Feb 13, 2017

I think you are installing ‘Yeoman’, which used to be called ‘yo’ — both the shell tool and the npm package.

It’s still the same software, and the ‘yo’ is used as CLI, but the package is now named ‘yeoman’.
Try this instead:

npm install -g yeoman

hemakh commented Feb 15, 2017

For yoeman, it is npm install -g yo taken from this http://yeoman.io/learning/

I tried with yoeman also i am getting the same error

AlexRouk commented Feb 15, 2017

Hello
I had similar issue and I found that it was related to firewall / proxy (the installation process tried and didn’t succeed to access some external content).

hope this will help someone..

amiraba commented Apr 1, 2017

Had the same issue.
Run the git bash or the command line console as an administrator when launching the npm install command
Worked for me ! 😉

npm-robot commented Jun 17, 2017

We’re closing this issue as it has gone seven days without activity and without being labeled. If we haven’t even labeled in issue in seven days then we’re unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you’re still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we’ve instituted them please see our blog post.

You can’t perform that action at this time.

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.

Источник

error installing with npm in windows 10 #398

Comments

brakdag commented May 25, 2018 •

npm i robotjs don’t work
not install in windows 10

Possible Solution

Context

Your Environment

• RobotJS version: npm version last
• Node.js version: 8.11.2
• npm version: 5.6.0
• Operating System: Windows 10 Home 64x

The text was updated successfully, but these errors were encountered:

antoniojps commented May 27, 2018 •

It might be worth updating Node before doing the instructions below.

Run this command from an administrative shell to install the «software» dependencias (Visual Studio, Python) on windows:
npm install —global —production windows-build-tools , recent feedback has been using npm install -g windows-build-tools as an alternative.

Install node-gyp globally:
npm install -g node-gyp

Then try installing the package again:
npm install robotjs

This solved the issue for me.

zircuitz commented May 30, 2018

I am having issues as well. Same Windows as @brakdag
I did install all the packages as @antoniojps mentions here. But when I try to initialize the library, I still get an error message:

sbucaille commented Jun 2, 2018

Same here, can’t install robotjs, I did what @antoniojps advised, the 3 commands, here is the last one :

Someone knows where does it come from ?

Deltatiger commented Jun 4, 2018

This seems to be a problem with the version requirements for NodeJS recompiled binaries.
The latest release does not have binaries for Windows 10 64Bit. When the node-pre-gyp fails due to lack of binaries, it falls back to building robotjs. For that you need some prerequisites, which are listed in the readme (https://github.com/octalmage/robotjs#building).
Can you try installing the required items and then trying again?

lgh06 commented Jul 7, 2018 •

cannot install either.
win10: 1803 17134.5
node: v8.11.1
npm: 5.6.0
with windows-build-tools installed.

lgh06 commented Jul 9, 2018

it worked, after I install a newer nodejs 8.11.3

pramodDesign commented Aug 17, 2018 •

When I try to run my project got following error:
0 info it worked if it ends with ok
1 verbose cli [ ‘C:\Program Files (x86)\nodejs\node.exe’,
1 verbose cli ‘C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js’,
1 verbose cli ‘start’ ]
2 info using npm@3.6.0
3 info using node@v5.6.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle imdevelopment-frontend@0.1.0 prestart: imdevelopment-frontend@0.1.0
6 silly lifecycle imdevelopment-frontend@0.1.0 prestart: no script for prestart, continuing
7 info lifecycle imdevelopment-frontend@0.1.0 start: imdevelopment-frontend@0.1.0
8 verbose lifecycle imdevelopment-frontend@0.1.0 start: unsafe-perm in lifecycle true
9 verbose lifecycle imdevelopment-frontend@0.1.0 start: PATH: C:\Program Files (x86)\nodejs\node_modules\npm\bin\node-gyp-bin;E:\im-frontend\frontend\node_modules.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\QuickTime\QTSystem;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files\Git\cmd;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\nodejs;C:\WINDOWS\System32\OpenSSH;C:\Ruby24-x64\bin;C:\Ruby24\bin;C:\Program Files\Microsoft VS Code\bin;C:\Users\vihnu pramod\AppData\Local\Microsoft\WindowsApps;C:\Users\vihnu pramod\AppData\Roaming\npm;
10 verbose lifecycle imdevelopment-frontend@0.1.0 start: CWD: E:\im-frontend\frontend
11 silly lifecycle imdevelopment-frontend@0.1.0 start: Args: [ ‘/d /s /c’, ‘npm-run-all -p watch-css start-js’ ]
12 silly lifecycle imdevelopment-frontend@0.1.0 start: Returned: code: 1 signal: null
13 info lifecycle imdevelopment-frontend@0.1.0

start: Failed to exec start script
14 verbose stack Error: imdevelopment-frontend@0.1.0 start: npm-run-all -p watch-css start-js
14 verbose stack Exit status 1
14 verbose stack at EventEmitter. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js 💯 13)
14 verbose stack at EventEmitter.emit (events.js:185:7)
14 verbose stack at ChildProcess. (C:\Program Files (x86)\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js 💯 13)
14 verbose stack at ChildProcess.emit (events.js:185:7)
14 verbose stack at maybeClose (internal/child_process.js:827:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid imdevelopment-frontend@0.1.0
16 verbose cwd E:\im-frontend\frontend
17 error Windows_NT 10.0.17134
18 error argv «C:\Program Files (x86)\nodejs\node.exe» «C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js» «start»
19 error node v5.6.0
20 error npm v3.6.0
21 error code ELIFECYCLE
22 error imdevelopment-frontend@0.1.0 start: npm-run-all -p watch-css start-js
22 error Exit status 1
23 error Failed at the imdevelopment-frontend@0.1.0 start script ‘npm-run-all -p watch-css start-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 imdevelopment-frontend package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error npm-run-all -p watch-css start-js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs imdevelopment-frontend
23 error Or if that isn’t available, you can get their info via:
23 error npm owner ls imdevelopment-frontend
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Deltatiger commented Sep 19, 2018

@pramodDesign What did you try to run? Could you give us more information?

A-312 commented Nov 28, 2018

19 error node v5.6.0
20 error npm v3.6.0

Источник

Installing Node.js (and npm) on Windows 10

I had some issues trying to install Node on Windows 10 and found the solution.

The error was as follows:

C:\Users\Stephan>npm
Error: ENOENT, stat ‘C:\Users\Stephan\AppData\Roaming\npm’

The solution is below.

8 Answers 8

Edit: It seems like new installers do not have this problem anymore, see this answer by Parag Meshram as my answer is likely obsolete now.

Original answer:

Follow these steps, closely:

• http://nodejs.org/download/ download the 64 bits version, 32 is for hipsters
• Install it anywhere you want, by default: C:\Program Files\nodejs
• Control Panel -> System -> Advanced system settings -> Environment Variables
• Select PATH and choose to edit it.

If the PATH variable is empty , change it to this: C:\Users\\AppData\Roaming\npm;C:\Program Files\nodejs

If the PATH variable already contains C:\Users\\AppData\Roaming\npm , append the following right after: ;C:\Program Files\nodejs

If the PATH variable contains information, but nothing regarding npm, append this to the end of the PATH: ;C:\Users\\AppData\Roaming\npm;C:\Program Files\nodejs

Now that the PATH variable is set correctly, you will still encounter errors. Manually go into the AppData directory and you will find that there is no npm directory inside Roaming. Manually create this directory.

Re-start the command prompt and npm will now work.

and hit the button that says «Download For . «

This’ll download the .msi (or .pkg for mac) which will do all the installation and paths for you, unlike the selected answer.

In addition to the answer from @StephanBijzitter I would use the following PATH variables instead:

So your new PATH would look like:

This has the advantage of neiter being user dependent nor 32/64bit dependent.

New installers (.msi downloaded from https://nodejs.org) have «Add to PATH» option. By default it is selected. Make sure that you leave it checked.

Everything should be installed in %appdata% (C:\Users\\AppData\Roaming), not ‘program files’.

The default MSI installer puts Node and the NPM that comes with it in ‘program files’ and adds this to the system path, but it sets the user path for NPM to %appdata% (c:\users[username]\appdata\roaming) since the user doesn’t have sufficient priveleges to write to ‘program files’.

This creates a mess as all modules go into %appdata%, and when you upgrade NPM itself — which NPM themselves recommend you do right away — you end up with two copies: the original still in ‘program files’ since NPM can’t erase that, and the new one inn %appdata%.

Even worse, if you mistakenly perform NPM operations as admin (much easier on Windows then on *nix) then it will operate on the ‘program files’ copy of NPM node_modules. Potentially a real mess.

So, when you run the installer simply point it to %appdata% and avoid all this.

And note that this isn’t anything wierd — it’s what would happen if you ran the installer with just user priveleges.

Источник