NodeJS-ошибка установки с NPM

Я устанавливаю определенный скрипт NodeJS -ласки. Но я не могу этого сделать. Я использую Windows 8.1, может кто-нибудь сказать мне, что это проблема я столкнулся, и почему эта установка не работает. Кажется, есть проблема с зависимостью buffertools, насколько я могу думать. Не знаю, как это можно исправить?

Если я загружаю сборку из github и помещаю ее в node-modules, ничего не работает. когда я пытаюсь начать, используя npm start, или во время реализации тоже.

12 ответов:

Как указано ниже, вам может не понадобиться устанавливать VS на windows, проверьте это

обновление 02/2016

некоторые плагины npm нужны node-gyp для установки.

однако, node-gyp имеет свои собственные зависимости (со страницы github):

обновление 09/2016

если вы с помощью Windows Теперь вы можете установить все node-gyp зависимости с помощью одной команды (Примечание: Запуск от имени администратора в Windows PowerShell):

а затем установить пакет

обновлено 06/2018

удалить $HOME/.узел-каталог gyp и повторите попытку.

Смотрите полную документацию здесь: node-gyp

убедитесь, что у вас есть все необходимое программное обеспечение для работы node-gyp :

вы можете настроить версию Visual Studio, используемую node-gyp через переменную окружения, так что вы можете избежать необходимости установки —msvs_version=2012 свойство каждый раз, когда вы делаете установку npm.

• set GYP_MSVS_VERSION=2012 для Visual Studio 2012
• set GYP_MSVS_VERSION=2013e (‘e’ означает Бесплатная экспресс-выпуск’)

Это все еще болезненно для пользователей Windows NodeJS, поскольку предполагается, что у вас установлена копия Visual Studio, и у многих конечных пользователей этого никогда не будет. Поэтому я лоббирую Joyent для поощрения их к включению веб-сокетов в качестве части основного узла, а также к возможному отправке компилятора GNU gcc в качестве части NodeJS установить, так что мы можем навсегда решить эту проблему.

не стесняйтесь добавлять свой голос на сайте:

я столкнулся с проблемой с ошибкой:

вот что я делал и что, наконец, сработало.

отказ от ответственности: Я просто получаю свои руки в узел, угловой после многих лет в мире Java, Linux и других.

Описание Окружающей Среды: Windows 8.1 64-разрядная; Cygwin; cygwin bash shell

используется, что привело к ошибке: npm install-g карма

: джип ЭРР! ошибка настройки джип ЭРР! ошибка стека: не удается найти исполняемый файл Python «python», вы можете установить PYT HON env variable.

Discovery: ‘какой python’ на оболочке bash ясно показывает ‘/ usr/bin / python’. Теперь это раздражает!

решение: это применимо только к тем, кто использует среду, аналогичную тому, что у меня есть, т. е. с помощью cygwin и bash shell. Надеюсь, что это поможет в других средах, как но имейте в виду, что ваш чайник чая может выглядеть немного иначе, чем мой.

1. во-первых, необходимо установить переменную $ PYTHON shell env.bashrc использует явный путь windows к исполняемому файлу python, а не корневой путь unix (/usr/bin), используемый cygwin.
2. во-вторых, и этот взял много проб / ошибок,и вот вам! Cygwin устанавливает python под /usr / bin (который на самом деле является зеркалом /bin в windows) с версией, т. е. (в моем system) / usr/bin / python2.7.exe, а затем добавляет ссылку / usr/bin / python —> python2.7.исполняемый. Проблема в том, что gyp не может следовать этой ссылке и продолжает давать раздражающую ошибку, что он не может найти python, хотя вы можете найти его просто отлично из командной строки оболочки.
3. с вышеуказанным фоном теперь добавьте следующую строку к вашему .bashrc

экспорт PYTHON=»C:/cygwin64/bin/python2.7.exe (или любая другая версия на вашем система)»

1. теперь источник вашей .bashrc из вашего домашнего каталога (на cygwin)—> ‘source .bashrc’

теперь вы должны быть в порядке, и gyp найдет исполняемый файл python.

Я надеюсь, что это поможет кому-то наткнуться на ту же или подобную проблему.

npm install not working in windows

I have no idea what is happening here. Hoping someone can help me.

This works great in my mac. But same process in Windows and npm install crashes. This is what I get.

I’ve tried everything I’ve seen in SO so far and every link Google search produced. I tried the following as suggested here:

Ran it as admin,

tried npm install -g

re-started xampp server

turned off Windows defender

checked the PATH for C:\Program Files\nodejs

Short of throwing this POS Windows threw a window, pun intended, I’ve done everything. Hail Apple!

node -v gives me a version v6.9.1

npm -v gives me a version as well 4.0.2

Which proves they are all installed fine, am I right?

5 Answers 5

After countless hours of debugging and researching, I decided to install in a different machine to see if the problem was with my Node installation. It worked.

So for everyone who may come across this, know that the possibility to uninstall node and delete NPM will be there. This is what I did. I believe it is the safest way to solve the problem and all the rest of your applications installed in your machine will still work. I credit this answer for these steps, although I had other npm and node_modules in other locations. So do a quick search for these and unless they are part of an application, make sure they are deleted as well.

Uninstall from Programs & Features with the uninstaller.

Reboot (or you probably can get away with killing all node-related processes from Task Manager).

Look for these folders and remove them (and their contents) if any still exist. Depending on the version you installed, UAC settings, and CPU architecture, these may or may not exist:

• C:\Program Files (x86)\Nodejs
• C:\Program Files\Nodejs
• C:\Users\\AppData\Roaming\npm (or %appdata%\npm )
• C:\Users\\AppData\Roaming\npm-cache (or %appdata%\npm-cache )
• C:\Users\\.npmrc (and possibly check for that without the . prefix too)

Check your %PATH% environment variable to ensure no references to Nodejs or npm exist.

If it’s still not uninstalled, type where node at the command prompt and you’ll see where it resides — delete that (and probably the parent directory) too.

NodeJS — Error installing with NPM

I am installing a certain NodeJS script — Caress. But i am not unable to. I am using Windows 8.1, can anyone tell me what is the problem i am facing, and why is this installation not working. There seems to be a problem with the buffertools dependency, thats far as i can think. Dont know how maybe fix this?

If i download the build from github and place it in node-modules, nothing seems to work. when i try to start, using npm start, or during implementation either.

14 Answers 14

UPDATED 02/2016

Some npm plugins need node-gyp to be installed.

However, node-gyp has it’s own dependencies (from the github page):

UPDATED 09/2016

If you’re using Windows you can now install all node-gyp dependencies with single command (NOTE: Run As Admin in Windows PowerShell):

and then install the package

UPDATED 06/2018

Delete your $HOME/.node-gyp directory and try again.

See full documentation here: node-gyp

Make sure you have all the required software to run node-gyp :

You can configure version of Visual Studio used by node-gyp via an environment variable so you can avoid having to set the —msvs_version=2012 property every time you do an npm install.

• set GYP_MSVS_VERSION=2012 for Visual Studio 2012
• set GYP_MSVS_VERSION=2013e (the ‘e’ stands for FREE ‘express edition’)

This is still painful for Windows users of NodeJS as it assumes you have a copy of Visual Studio installed and many end users will never have this. So I’m lobbying Joyent to the encourage them to include web sockets as part of CORE node and also to possible ship a GNU gcc compiler as part of NodeJS install so we can permanently fix this problem.

Feel free to add your vote at:

I encountered the issue with the error:

Here is what I was doing and what finally worked.

Disclaimer: I am just getting my hands into Node, Angular after many years in the Java, Linux world among others.

Environment Description: Windows 8.1 64-bit; Cygwin; cygwin bash shell

Command used that led to error: npm install -g karma

Error: gyp ERR! configure error gyp ERR! stack Error: Can’t find Python executable «python», you can set the PYT HON env variable.

Discovery: ‘which python’ on bash shell clearly shows ‘/usr/bin/python’. Now that is annoying!

Solution: This is only applicable to those using the environment similar to what I have, i.e. using cygwin and bash shell. Hope it helps in other environments as well but keep in mind that your kettle of tea may look a little different than mine.

1. Firstly, need to set the $PYTHON shell env variable in .bashrc using the explicit windows path to the python executable and not the unix like root path (/usr/bin) used by cygwin.
2. Secondly, and this one took a lot of trial/error and here’s the gotcha! Cygwin installs python under /usr/bin (which is really a mirror of /bin on windows) with the version, i.e. (in my system) /usr/bin/python2.7.exe and then adds a link /usr/bin/python —> python2.7.exe. The problem is that gyp cannot follow this link and keeps giving the annoying error that it cannot find python even though you can find it just fine from the shell command line.
3. With the above background now add the following line to your .bashrc

export PYTHON=»C:/cygwin64/bin/python2.7.exe (or whatever is the version on your system)»

1. Now source your .bashrc from your home directory (on cygwin)—> ‘source .bashrc’

You should be fine now and gyp will find the python executable.

I hope this helps someone stumbling on the same or similar issue.

Npm Error — Windows NT — How to resolve

I get the following error when I try npm install :

What is wrong? I cant use nodejs 0.11

9 Answers 9

You may want to point to a local registry or a registry behind the firewall

Change your location of cache. This will definitely work. By default NPM tries to pickup packages from cache and the default location is sometimes prohibited from reading.

npm config set cache C:\Dev\nodejs\npm-cache —global

Updating npm solved the problem for me. npm install -g npm

Culprit: Windows real time protection

Turn off the real time protection of Windows Defender (or any other anti-virus) and you will be good to go. I spent a lot of time finding this simple solution but it really works.

Seems it is a certificate expire issue with:

Problem caused by my corporate proxy. Here is solution that worked for me: In the

file with next structure:

use http regitstry if https is blocked by your corporate proxy

You are probably behind a proxy or firewall. Ref. this issue.

To resolve the issue disable any firewall, proxy or antivirus that might interfere.

Check the information at the log file generated at the same folder you issued the command:

In my case the error was related a mistake made during typing the content of the package.json:

This error mostly occurs when you use any defender in windows or antivirus software. I have disabled Antivirus software and work right. if a problem does not solve then start your CMD administrator mode and you should point a local registry

Not the answer you’re looking for? Browse other questions tagged node.js npm or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.4.16.39093

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

npm ERR! Windows_NT 10.0.14393 #13979

Comments

zagorodnik commented Sep 16, 2016

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

KenanY commented Sep 16, 2016

@zagorodnik Does C:\Users\Alex\WebstormProjects\Angular2\package.json exist?

Eruoghene commented Sep 20, 2016

i’m having same issue. if it doesn’t how can i get it?

KenanY commented Sep 20, 2016

@Eruoghene You can create one with npm init . Make sure to define a «start» script inside it too before running npm start .

ganeshMNAIK commented Oct 25, 2016

how can i fix this error.
D:\angular2-demo>npm start
npm ERR! Windows_NT 10.0.14393
npm ERR! argv «C:\Program Files\nodejs\node.exe» «C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js» «start»
npm ERR! node v4.6.1
npm ERR! npm v2.15.9
npm ERR! file D:\angular2-demo\package.json
npm ERR! code EJSONPARSE

npm ERR! Failed to parse json
npm ERR! Unexpected token ‘:’ at 2:9
npm ERR! «name»: «angular2-demo»,
npm ERR! ^
npm ERR! File: D:\angular2-demo\package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse

npm ERR! Please include the following file with any support request:
npm ERR! D:\angular2-demo\npm-debug.log

KenanY commented Oct 25, 2016

@zagorodnik Could you provide the entire D:\angular2-demo\package.json ?

ThaiQuocTuan2016 commented Oct 29, 2016

John, thank you for reporting this issue.
What shell environment are you using (native windows command shell, mingw, cygwin)?
Can you please provide the output of the following two commands:
$ patch -v
$ snyk protect -d # please run it in project folder
Thanks! We managed to reproduce the issue locally. Please uninstall old version of gnu patch, and use official git tools instead (https://git-scm.com/download/win). Make sure to add the bin folder (C:\Program Files\Git\usr\bin) to the PATH.
running patch -v should have the following output:

GNU patch 2.7.5
Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc.
Copyright (C) 1988 Larry Wall

License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Larry Wall and Paul Eggert

ThaiQuocTuan2016 commented Oct 29, 2016

C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp>patch -v
GNU patch 2.7.5
Copyright (C) 2003, 2009-2012 Free Software Foundation, Inc.
Copyright (C) 1988 Larry Wall

License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Larry Wall and Paul Eggert

mean@0.7.0 postinstall C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp
node tools/scripts/postinstall.js

Auto installing package dependencies
bower web-bootstrap#* copy C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp\node_modules\meanio\resources\web-bootstrap.js
bower jquery#* cached https://github.com/jquery/jquery-dist.git#3.1.1
bower jquery#* validate 3.1.1 against https://github.com/jquery/jquery-dist.git#*
bower angular#* cached https://github.com/angular/bower-angular.git#1.5.8
bower angular#* validate 1.5.8 against https://github.com/angular/bower-angular.git#*
bower angular-resource#* cached https://github.com/angular/bower-angular-resource.git#1.5.8
bower angular-resource#* validate 1.5.8 against https://github.com/angular/bower-angular-resource.git#*
bower angular-cookies#* cached https://github.com/angular/bower-angular-cookies.git#1.5.8
bower angular-cookies#* validate 1.5.8 against https://github.com/angular/bower-angular-cookies.git#*
bower angular-route#* cached https://github.com/angular/bower-angular-route.git#1.5.8
bower angular-route#* validate 1.5.8 against https://github.com/angular/bower-angular-route.git#*
bower angular-mocks#* cached https://github.com/angular/bower-angular-mocks.git#1.5.8
bower angular-mocks#* validate 1.5.8 against https://github.com/angular/bower-angular-mocks.git#*
bower bootstrap#* cached https://github.com/twbs/bootstrap.git#3.3.7
bower bootstrap#* validate 3.3.7 against https://github.com/twbs/bootstrap.git#*
bower angular-ui-select#* cached https://github.com/angular-ui/ui-select.git#0.19.6
bower angular-ui-select#* validate 0.19.6 against https://github.com/angular-ui/ui-select.git#*
bower angular-ui-router#* cached https://github.com/angular-ui/angular-ui-router-bower.git#0.3.1
bower angular-ui-router#* validate 0.3.1 against https://github.com/angular-ui/angular-ui-router-bower.git#*
bower angular-bootstrap#* cached https://github.com/angular-ui/bootstrap-bower.git#2.2.0
bower angular-bootstrap#* validate 2.2.0 against https://github.com/angular-ui/bootstrap-bower.git#*
bower angular-sanitize#* cached https://github.com/angular/bower-angular-sanitize.git#1.5.8
bower angular-sanitize#* validate 1.5.8 against https://github.com/angular/bower-angular-sanitize.git#*
bower web-bootstrap#* resolved C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp\node_modules\meanio\resources\web-bootstrap.js
Updating Bower dependenciesadata: sill mapToRegistry uri https://registry.npmjs.org/libbase64
mean@0.7.0 C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp
+— meanio-admin@0.1.7 (git://github.com/linnovate/meanio-admin.git#0e9d428c67789aadf5615f7d1a109716d3375ad4)
+— meanio-circles@0.1.1 (git://github.com/linnovate/meanio-circles.git#3fd8e32af3374dcfc34026b7f86e9d332df2b3a6)
+— meanio-system@0.1.3 (git://github.com/linnovate/meanio-system.git#a1b1b2b35eec858493d3a308e56d1e2014627ed5)
`— meanio-users@0.1.4 (git://github.com/linnovate/meanio-users.git#b1084c608bbf17e879668e1392a664919151fa42)

mean@0.7.0 prepublish C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp
npm run snyk-protect

mean@0.7.0 snyk-protect C:\Users\Tuan_Pro\Desktop\TTTN\TST\myApp
snyk protect

Successfully applied Snyk patches
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted <"os":"darwin","arch":"any">(current: <"os":"win32","arch":"x64">)

plmachado commented Nov 7, 2016

npm ERR! getaddrinfo EAGAIN
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Pedro\Desktop\app\app\npm-debug.log

legodude17 commented Nov 7, 2016

@plmachado, that is a different issue. Check your internet connection and then open a new issue if the problem persists.

vgoreiko commented Nov 18, 2016

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.9
3 info using node@v7.1.0
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle angular2-typescript-webpack@1.3.0 prestart: angular2-typescript-webpack@1.3.0
6 silly lifecycle angular2-typescript-webpack@1.3.0 prestart: no script for prestart, continuing
7 info lifecycle angular2-typescript-webpack@1.3.0 start: angular2-typescript-webpack@1.3.0
8 verbose lifecycle angular2-typescript-webpack@1.3.0 start: unsafe-perm in lifecycle true
9 verbose lifecycle angular2-typescript-webpack@1.3.0 start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;F:\mainSite\node_modules.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Program Files\Microsoft SQL Server\110\Tools\Binn;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\Git\cmd;C:\Program Files\nodejs;C:\Program Files\TortoiseGit\bin;C:\Users\админ\AppData\Local\Microsoft\WindowsApps;C:\Users\админ\AppData\Roaming\npm
10 verbose lifecycle angular2-typescript-webpack@1.3.0 start: CWD: F:\mainSite
11 silly lifecycle angular2-typescript-webpack@1.3.0 start: Args: [ ‘/d /s /c’, ‘webpack-dev-server’ ]
12 silly lifecycle angular2-typescript-webpack@1.3.0 start: Returned: code: 3221226505 signal: null
13 info lifecycle angular2-typescript-webpack@1.3.0

start: Failed to exec start script
14 verbose stack Error: angular2-typescript-webpack@1.3.0 start: webpack-dev-server
14 verbose stack Exit status 3221226505
14 verbose stack at EventEmitter. (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. (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:885:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid angular2-typescript-webpack@1.3.0
16 verbose cwd F:\mainSite
17 error Windows_NT 10.0.14393
18 error argv «C:\Program Files\nodejs\node.exe» «C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js» «start»
19 error node v7.1.0
20 error npm v3.10.9
21 error code ELIFECYCLE
22 error angular2-typescript-webpack@1.3.0 start: webpack-dev-server
22 error Exit status 3221226505
23 error Failed at the angular2-typescript-webpack@1.3.0 start script ‘webpack-dev-server’.
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 angular2-typescript-webpack package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error webpack-dev-server
23 error You can get information on how to open an issue for this project with:
23 error npm bugs angular2-typescript-webpack
23 error Or if that isn’t available, you can get their info via:
23 error npm owner ls angular2-typescript-webpack
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Please, help. Everything works on another machine.

legodude17 commented Nov 18, 2016

As the error says, this is a problem with the angular2-typescript-webpack package. Please try running ./node_modules/.bin/webpack-dev-server . If it succeeds then tell me, otherwise go bug the author.

vgoreiko commented Nov 22, 2016

Hi, guys. At least solved current issue by removing node.js of version 7.1.0 and installing 7.0.0. Hope, that it`ll helps someone.
Enjoy.

juaniliska commented Dec 26, 2016

i have the same problem and to fix run

• npm config get registry
• npm cache clean
• npm install express

later
-npm start

and work the tutorial of angular2 (no working in the first time)
D:\Angular2\juan\quickstart>npm start

angular-quickstart@1.0.0 start D:\Angular2\juan\quickstart
tsc && concurrently «tsc -w» «lite-server»