Содержание
- NodeJS-ошибка установки с NPM
- 12 ответов:
- обновление 02/2016
- обновление 09/2016
- обновлено 06/2018
- Node Interpreter: node (No executable found in $PATH) Follow
- Votes
- Share
- [WIN] Where is the executable PATH? #1258
- Comments
- seanvree commented Aug 8, 2017 •
- bnoordhuis commented Aug 8, 2017
- refack commented Aug 8, 2017
- seanvree commented Aug 8, 2017
- bnoordhuis commented Aug 8, 2017
- seanvree commented Aug 8, 2017
- bnoordhuis commented Aug 8, 2017
- seanvree commented Aug 8, 2017 •
- refack commented Aug 8, 2017
- [coc.nvim] node is not executable (node installed by nvm) #856
- Comments
- sandangel commented Jun 9, 2019 •
- Describe the bug
- Reproduce the bug
- chemzqm commented Jun 9, 2019 •
- Muzietto commented Dec 16, 2019
- LukeAI commented Jan 28, 2020
- oblitum commented Jan 28, 2020
- chemzqm commented Jan 31, 2020
- lucasdf commented Feb 16, 2020
- yujinyuz commented Mar 1, 2020
- kirbygit commented Mar 21, 2020 •
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. Надеюсь, что это поможет в других средах, как но имейте в виду, что ваш чайник чая может выглядеть немного иначе, чем мой.
- во-первых, необходимо установить переменную $ PYTHON shell env.bashrc использует явный путь windows к исполняемому файлу python, а не корневой путь unix (/usr/bin), используемый cygwin.
- во-вторых, и этот взял много проб / ошибок,и вот вам! Cygwin устанавливает python под /usr / bin (который на самом деле является зеркалом /bin в windows) с версией, т. е. (в моем system) / usr/bin / python2.7.exe, а затем добавляет ссылку / usr/bin / python —> python2.7.исполняемый. Проблема в том, что gyp не может следовать этой ссылке и продолжает давать раздражающую ошибку, что он не может найти python, хотя вы можете найти его просто отлично из командной строки оболочки.
- с вышеуказанным фоном теперь добавьте следующую строку к вашему .bashrc
экспорт PYTHON=»C:/cygwin64/bin/python2.7.exe (или любая другая версия на вашем система)»
- теперь источник вашей .bashrc из вашего домашнего каталога (на cygwin)—> ‘source .bashrc’
теперь вы должны быть в порядке, и gyp найдет исполняемый файл python.
Я надеюсь, что это поможет кому-то наткнуться на ту же или подобную проблему.
Node Interpreter: node (No executable found in $PATH) Follow
Trying to execute simple JaveScript code in IntelliJ IDEA:
When I try to run it brings up the Edit configuration window.
I click on the . and then the + sign to add a local, but I can’t find the node.
I do have the Node.js and Node.js Remote Interpreter plugins installed and enabled.
My IDEA application installed in the default location: /usr/local/bin/
But I can’t see node there.
I can see the hidden files.
How might I be able to find the node?
I also have a similar error when trying to use the «JavaScript for Beginners» course on for the Learn and Teach plugin.
Your help is greatly appreciated!
Votes
You need to install node.js itself and have a binary on the system that you can run from the terminal: https://nodejs.org/en/ .
Thank you Serge!
I really appreciate it!
For others out there, I went to the link above, clicked on one of the downloads, installed it.
It showed the default location as /usr/local/bin/node and I accepted.
Once it finished installing, I checked the Languages and Frameworks for Node.js and NPM and it had already updated the Node interpreter with the file path.
If it works with the regular installer, it means Webstorm is incompatible with NVM. Node is installed via NVM and on the PATH, but Webstorm has some sort of dependency on the official installer.
@Jason Tiscione No, it doesn’t seem to have any relation to having Node.js installed with NVM
The problem I’m having is that all the features in the Run menu are broken.
Node is on the PATH. If I open up the Terminal tab and type «which node» it prints the location of the current executable in NVM. If I type echo $PATH I can see it. But if I create a node or npm run target, the «Node Interpreter» dropdown says «node: NO EXECUTABLE FOUND IN PATH».
So I try specifying the absolute path to the NVM folder’s node executable in the dropdown instead. But if I try to run it, it still crashes and complains that node is not on the PATH:
«/home/jason/.nvm/versions/node/v12.18.0/bin/node /home/jason/.nvm/versions/node/v12.18.0/lib/node_modules/npm/bin/npm-cli.js start
npm WARN lifecycle npm is using /home/jason/.nvm/versions/node/v12.18.0/bin/node but there is no node binary in the current PATH.»
/usr/bin/env: ‘node’: No such file or directory
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! the-nextjs-starter@1.0.0 start: `nodemon server.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the the-nextjs-starter@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/jason/.npm/_logs/2020-07-09T18_39_03_936Z-debug.log
Process finished with exit code 1
So I try copy/paste of the command line that Webstorm claims to be running. It works with no problems, both inside and outside Webstorm’s terminal. So this is obviously a bug in Webstorm.
I tried downgrading to 2019.3.3 but that version is also broken.
[WIN] Where is the executable PATH? #1258
Node Version:
NODE: v6.11.1
NPM: 5.3.0
Platform:
Window 10E x64 1703
Compiler:
VS2015
Module:
Sorry if this is a noob question, but I can’t seem to figure this out.
I installed node-gyp fine from C:node-gyp, but it’s not being added to my PATH.
Where is the executable to add to my PATH?
The text was updated successfully, but these errors were encountered:
You don’t usually have to install node-gyp yourself. It’s bundled with npm and npm takes care of executing it when installing modules that need it.
Plus a general windows tip, you can run where node-gyp or where npm in a cmd.exe console, and cmd will tell you where the files it can run are. For example:
I do understand both of your points, and that SHOULD work, but it’s not in my environment for some reason despite a successful install as you see in my OP. Which is why I was asking how to manually add it to my PATH because I can’t seem to invoke node-gyp:
If you installed node-gyp with npm install -g , then it’s wherever npm puts global binaries. See https://stackoverflow.com/questions/33819757/global-npm-install-location-on-windows for more info.
Right, I’ve got that DIR, and I can navigate to it, but again, how do I launch node-gyp from that DIR? . or any Directory?
Where is the actual .exe or .bat file?
There should be a node-gyp.cmd in that directory, unless you have bin-links set to false in your npm config.
I don’t want to cut this conversation short but your questions are really about npm, not node-gyp. Happy to help if you can’t figure something out but see if you can find the answer in npm’s documentation first.
with all due respect, I run many many NPM and Node packages without issue. I simply followed your exact instructions, and I can’t run your specific package. That’s all. I’m trying to understand what I’m doing wrong here.
I DO NOT have a node-gyp.cmd in that DIR.
@seanvree node-gyp (and any other global npm packages) uses an npm mechanism to create the «shim» that is used to run the the CLI endpoint of the package (in this case node-gyp.cmd ).
npm puts it in the directory pointed to by npm config get prefix
You can run these two commands and check that the npm global directory is in your %Path%
this will show you npm ‘s configuration
this will pretty print the directories in your %Path%
[coc.nvim] node is not executable (node installed by nvm) #856
sandangel commented Jun 9, 2019 •
Describe the bug
When installed with nvm, node when we first started the shell is a function defined in nvm scripts. So if we use executable to check, the error will be shown as above
Reproduce the bug
open the shell, execute nvim , the error above will show up
run which node :
run node -v && nvim , the error will no longer show
I think We should change the executable(‘node’) check to something else, because most of node users is using nvm to install node
The text was updated successfully, but these errors were encountered:
because most of node users is using nvm to install node
I can’t agree, since nvm sucks on many cases.
Use let g:coc_node_path = ‘/path/to/node’ when you can’t use node in your $PATH.
because most of node users is using nvm to install node
I can’t agree, since nvm sucks on many cases.
This personal opinion regarding nvm is irrelevant to the true fact mentioned by the OP.
Please reconsider providing a user-friendly feature for solving this annoying issue.
So how do I resolve this? I have just installed neovim and coc.nvim on a fresh ubuntu 16.04 system. Do I have to install nodejs?
just set the variable as suggested. nvm will have the node executable somewhere.
@LukeAI Make node in your $PATH
Cool! Had this same problem after removing the system’s node and replacing it by n node installation.
At the end, the problem happened when my i3 shortcuts were launching NVIM with /bin/sh instead of bash. When using sh my custom node’s bin location was not in the path, since my export command is in bashrc and sh sources .profile instead.
You can debug it by using echo executable(‘node’) which will return 1 if it exists and is executable, and by using echo $PATH to print the environment variables considered by NVIM context.
As mentioned by people above, setting the path by using let g:coc_node_path = ‘/path/to/node’ works. However, you must use the full path /home/xxx/path/to/node .
I also had the same problem. I’m using Fish shell with nvm (https://github.com/FabioAntunes/fish-nvm)
Luckily, fish-nvm provides nvm_alias_command that creates binaries under /usr/local/bin .
So, what I did was I just executed nvm_alias_command node and coc is working again
My linux pc got corrupted and decided to install ubuntu and had to re-install everything. As I download zsh I encountered this problem. May I ask where can I put this single line?
let g:coc_node_path = ‘/path/to/node’
do I just put that somewhere in coc.vim or am I wrong.
With a downloaded and installed version of Visual Studio Code 1.2.1, and a 64bit version of node.exe msi placed in my working directory (I am assuming that is correct), how do we add node and npm command line tools to be on our PATH? I am confused in understanding that statement. Where and how do we implement that? I am quoting this requirement directly from the top of this resource page — https://code.visualstudio.com/Docs/runtimes/nodejs
As a result of my current situation, I set a break-point in an app.js file. And when I hit F5, it tells me…
Cannot find runtime 'node' on PATH
I am completely lost in understanding and fixing this issue in Visual Studio Code.
asked Jun 14, 2016 at 22:30
klewisklewis
7,15415 gold badges56 silver badges99 bronze badges
5
On OSX and VSCode 1.56.2 all I had to do was to close and restart VSCode and the problem went away.
answered Dec 18, 2018 at 17:39
David DehghanDavid Dehghan
20.7k8 gold badges103 silver badges92 bronze badges
11
first run below commands as super user
sudo code . --user-data-dir='.'
it will open the visual code studio import the folder of your project and set the launch.json as below
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch Program",
"program": "${workspaceFolder}/app/release/web.js",
"outFiles": [
"${workspaceFolder}/**/*.js"
],
"runtimeExecutable": "/root/.nvm/versions/node/v8.9.4/bin/node"
}
]
}
path of runtimeExecutable will be output of "which node"
command.
Run the server in debug mode.
user
4,3335 gold badges17 silver badges34 bronze badges
answered Jul 19, 2018 at 13:33
anuj ranaanuj rana
9826 silver badges2 bronze badges
2
To follow up, I just ran into this as well. When I installed Node.js there was an option that said Add to PATH (Available After Restart). Seems like Windows just needs a restart to make things work.
answered Jul 16, 2016 at 18:25
3
Quick fix that works for me. Navigate to the root directory of your folder from command line (cmd). then once you are on your root directory, type:
code .
Then, press enter. Note the «.», don’t forget it. Now try to debug and see if you get the same error.
answered Mar 14, 2017 at 14:59
3
Apply a Default Node Version via NVM
I’m using macOS Big Sur and setting the default version via nvm
fixed this for me by running this command: nvm alias default 16
(change 16
to the version you want as your default).
Note that node
worked fine in the terminal for me (both with zsh and bash) but not when running via the vscode debugger and I already had the following config in both ~/.zshrc and ~/.bash_profile to load in nvm
:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion
It wasn’t until I set the default Node version that vscode would launch node targets just fine.
answered Apr 9, 2021 at 23:40
SamSam
26.7k12 gold badges73 silver badges101 bronze badges
3
I did which node
on my terminal:
/usr/local/bin/node
and then i added
"runtimeExecutable": "/usr/local/bin/node"
in my json file.
answered May 21, 2019 at 15:46
ASHISH RASHISH R
3,8851 gold badge20 silver badges16 bronze badges
2
For me, the node
binary is in PATH
and I can run it from the terminal (iTerm or Terminal), and the Terminal apps are set to use zsh
If you are on a Mac, with iTerm and Zsh, please use the following VSCode settings for Node to work.
After this change, you can get rid of this line from your launch.json
config file. (the debug settings in VSCode)
"runtimeExecutable": "/usr/local/bin/node"
If this doesn’t work, make sure you choose the default shell as zsh
. To do this,
-
Open the command palette using Cmd+Shift+P
-
Look for the
Terminal: Select Default Shell
command
-
Select
zsh
from the options
answered Jun 11, 2020 at 18:26
So node got kicked out of path. you can do
SET PATH=C:Program FilesNodejs;%PATH%
Or simply reinstall node to fix this. which ever you think is easiest for you
answered Jun 14, 2016 at 22:33
irimawiirimawi
3381 silver badge9 bronze badges
3
Had the same issue and in my case it was a problem with a vs code extension. Try running code as:
$ code --disable-extensions
Once in the editor, I ran my program in the debug mode and worked, and then started code with
$ code
And it continued working fine.
Hope it works for you.
Duck Dodgers
3,3197 gold badges29 silver badges42 bronze badges
answered Jan 3, 2019 at 12:15
SebastianSebastian
1612 silver badges3 bronze badges
0
I had a similar issue with zsh and nvm on Linux, I fixed it by adding nvm initialization script in ~/.profile
and restart login session like this
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
answered Mar 19, 2019 at 10:54
I use /bin/zsh
, and I changed vscode to do the same, but somehow vscode still use the path from /bin/bash
. So I created a .bash_profile file with node location in the path.
Simply run in terminal:
echo "PATH=$PATH
export $PATH" >> ~/.bash_profile
Restart vscode, and it will work.
answered Nov 3, 2020 at 9:53
ShlShl
2,6201 gold badge15 silver badges16 bronze badges
I also ran into this error. Restart the PC works for me.
answered Feb 17, 2017 at 13:42
Umair AkbarUmair Akbar
5485 silver badges10 bronze badges
1
Do not launch the VS code from the start menu separately. Use
$Code .
command to launch VS code. Now, create your file with the extension .js and Start debugging (F5) it. It will be executed.
Otherwise, restart your system and follow the same process.
answered Jul 10, 2018 at 10:31
The cause for me receiving this error was trying the new pre-release VSCode JS debugger.
If you opted in, change via User settings:
"debug.javascript.usePreview": true|false
Everything in my normal configuration and integrated terminal was correct and finding executables. I wasted a lot of time trying other things!
answered Apr 20, 2020 at 19:41
3
(CMD+SHIFT+P) Shell command: Install ‘code’ command in PATH
should do the trick!
answered Jul 26, 2021 at 15:12
TellisenseTellisense
1,71811 silver badges11 bronze badges
1
i resolved this problem after disable ESLint
extention.
answered Apr 19, 2020 at 8:11
I am on OSX, this did not work for me:
code . --user-data-dir='.'
but this DID work:
code . -data-dir='.'
answered Apr 19, 2020 at 10:23
Just relaunch your project from the termial
e.g. yourprojectdir code .
answered Dec 5, 2022 at 7:52
This is the solution according to the VS code debugging page.
This worked for my setup on Windows 10.
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "Launch Program",
"program": "${file}"
}
The solution is here:
https://code.visualstudio.com/docs/editor/debugging
Here is the launch configuration generated for Node.js debugging
answered Jun 3, 2020 at 19:39
D.LD.L
3,7574 gold badges20 silver badges39 bronze badges
I also encountered this issue. Did the following and it got fixed.
- Open your computer terminal (not VSCode terminal) and type node —version to ensure you have node installed. If not, then install node using nvm.
- Then head to your bash file (eg .bashrc, .bash_profile, .profile) and add the PATH:
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
- If you have multiple bash files, you ensure to add the PATH to all of them.
- Restart your VSCode terminal and it should be fine.
answered Jun 9, 2020 at 4:46
Mine was more project specific. We use «Auto Reload» to run our launch.json for the backend. The error states the file path of the runtimeExecutable
and allows you to open launch.json
. In my launch.json case:
"runtimeExecutable": "${workspaceFolder}/functions/node_modules/.bin/nodemon"
I tried the restarts and answers here originally but no luck, so I manually explored into my functions/node_modules
folder and realized .bin
was missing. I used my terminal to path into functions
like so:
cd functions
Terminal directory path example: ( ~/OneDrive/Desktop/{project dir covered}/{project dir covered}/functions )
Then I did an npm install using npm i
, and now everything is back to normal. Keep in mind, most of these answers are general fixes. If your situtation is more specific, be sure to break it down from the start. Hope this might help others!
answered Jun 22, 2022 at 20:14
Содержание
- Arch Linux
- #1 2016-11-26 19:21:08
- [SOLVED] Node: npm install package but no executable found
- #2 2016-11-27 12:15:58
- Re: [SOLVED] Node: npm install package but no executable found
- #3 2016-11-28 15:58:53
- Re: [SOLVED] Node: npm install package but no executable found
- #4 2016-11-28 20:50:36
- Re: [SOLVED] Node: npm install package but no executable found
- #5 2016-11-29 13:10:49
- Re: [SOLVED] Node: npm install package but no executable found
- Node не распознается как внутренняя или внешняя команда, а находится в PATH
- ОТВЕТЫ
- Ответ 1
- Ответ 2
- Ответ 3
- Ответ 4
- Ответ 5
- Ответ 6
- Ответ 7
- Возможное решение
- Ответ 8
- Ответ 9
- Ответ 10
- how can I find my node.js files in linux, /usr/bin/node is not working
- 4 Answers 4
- [coc.nvim] node is not executable (node installed by nvm) #856
- Comments
- sandangel commented Jun 9, 2019 •
- Describe the bug
- Reproduce the bug
- chemzqm commented Jun 9, 2019 •
- Muzietto commented Dec 16, 2019
- LukeAI commented Jan 28, 2020
- oblitum commented Jan 28, 2020
- chemzqm commented Jan 31, 2020
- lucasdf commented Feb 16, 2020
- yujinyuz commented Mar 1, 2020
- kirbygit commented Mar 21, 2020 •
- yujinyuz commented Mar 21, 2020
- fannheyward commented Mar 21, 2020
- kirbygit commented Mar 22, 2020
- dagadbm commented Jun 8, 2020
- chemzqm commented Jun 9, 2020
- 5ilvers commented Jul 17, 2020
- ShiromMakkad commented Feb 8, 2022 •
- tmpm697 commented May 3, 2022
- Cannot install NodeJs: /usr/bin/env: node: No such file or directory
- 19 Answers 19
Arch Linux
You are not logged in.
#1 2016-11-26 19:21:08
[SOLVED] Node: npm install package but no executable found
I uncommented prefix and set:
prefix=/home/gleiton/.node_modules
and added
But after installing express
and opening a new terminal:
As we can see, there is no bin directory, neither in
/.node_modules nor in /usr/lib/node_modules.
And, no executable known as «express»
Last edited by gleiton (2016-11-29 13:34:18)
#2 2016-11-27 12:15:58
Re: [SOLVED] Node: npm install package but no executable found
Are you sure that setting the prefix took effect? Browsing through the wiki page you linked to, I suggest you try
and report back on whether that was successful.
#3 2016-11-28 15:58:53
Re: [SOLVED] Node: npm install package but no executable found
@robg thanks for the tip. I chose setting prefix by npm config edit, and I’ve seen files were copied there.
Anyway I executed your command line, logged in again but nothing.
Files related to express are installed, but no command «express», and no «bin» directory.
#4 2016-11-28 20:50:36
Re: [SOLVED] Node: npm install package but no executable found
I checked it out myself and you are right. However the solution to your problem is not far: If you check
/.node_modules/lib/node_modules/express and have a look at the content of the Readme.md file in that folder you’ll notice that the command line utility for express is apparently in a separate package called «express-generator». In fact executing
did the trick for me.
#5 2016-11-29 13:10:49
Re: [SOLVED] Node: npm install package but no executable found
Great! That worked for me too. Now there’s something in bin/ path.
Maybe my book is outdated, but the documentation is clear. Reading the old Readme is always a good idea.
Thanks a lot @robg, I think I can put a «Solved» on this issue, with «perfect» rsrs.
Источник
Node не распознается как внутренняя или внешняя команда, а находится в PATH
Хотя я следую советам:
Я следил за предложениями в SO, добавляя переменную к переменным среды и отображая Ok в пути:
Следующая строка не будет выполнена
Но если я перейду в список папок в Path, то он будет работать нормально.
ОТВЕТЫ
Ответ 1
Каталог nodejs в вашем PATH не распознается, потому что перед точкой с запятой существует пробел, поэтому Windows ищет каталог с пробелом в конце имени, которого не существует.
Ответ 2
Ошибка: ‘node’ не распознается как внутренняя или внешняя команда
Проблема может заключаться в том, что node не установлен на компьютере, на котором работает приложение.
Затем установите его и установите переменную среды для nodejs.
Еще одной причиной может быть путь nodejs, который не задан в переменной среды.
Обратите внимание на следующее: открыть панель управления → Система и безопасность → Система → Расширенные настройки системы → Переменные среды → Путь
путь nodejs должен быть доступен здесь. Если недоступно, добавьте следующее:
C:Program Files (x86)nodejs ИЛИ C:Program Filesnodejs
Теперь перезапустите приложение, и ошибка была решена.
Ответ 3
Слэш послеnodejsработал у меня
Ответ 4
Обычно переменные среды не действуют до тех пор, пока система Restart.
Я предлагаю System Restart для всех тех, кто сталкивается с той же проблемой при выполнении чистой установки.
Это сработало для меня.
Ответ 5
Ответ 6
В Windows вам необходимо установить путь к папке node.js в системные переменные или пользовательские переменные.
1) откройте Панель управления → Система и безопасность → Система → Расширенные настройки системы → Переменные среды
3) Перезагрузите среду IDE или компьютер.
Полезно также добавить пути «npm» и «Git» как переменные, разделенные точкой с запятой.
Ответ 7
Если вы проверили свой PATH и уверены, что путь для node добавлен правильно, то вы, вероятно, столкнетесь с проблемой во время выполнения команд node OR npm с CLI, отличным от интерфейс командной строки по умолчанию для операционной системы (например, Git bash в Windows).
Возможное решение
Попробуйте запустить node с терминалом по умолчанию для вашей ОС.
Ответ 8
Я столкнулся с этой проблемой даже после добавления node.exe в PATH. Я не смог запустить команду node в случайных местах без запуска командной строки в качестве администратора.
Решение этой проблемы заключается в том, что вы должны предоставить полный доступ к этому файлу node.exe для разных типов пользователей. откройте свойства node.exe, перейдите на вкладки безопасности, проверьте все параметры безопасности для пользователя на локальном компьютере.
после этого вы сможете получить доступ к node.exe файлу из любого места.
Ответ 9
И следующее решение:
Ответ 10
Это так же просто, как добавить расположение nodejs ( C:Program Files (x86)nodejs ) в вашу переменную PATH и перезапустить приложение с помощью «Запуск от имени администратора».
Источник
how can I find my node.js files in linux, /usr/bin/node is not working
I want to find where is my node.js in ubuntu linux system, the command: which node gives me the path of /usr/bin/node, but when I go to that folder, there is no node folder and files.
can somebody help me?
I installed the node.js by this:
4 Answers 4
In order to find the installation path write the below command in the terminal:
If it doesn’t succeed, try this one:
Same thing for finding npm installation path:
If you are on Windows, write where instead of which
don’t worry sudo apt-get install nodejs installs a version of nodejs which is normally outdated. /usr/bin/nodejs is therefore fine.
Do some additional work to use only node for the command line:
install package manager npm: sudo apt-get install npm
You can downgrade node to a desired version, e.g: sudo n 0.12.4
If you have both Nodejs and npm installed correctly, just open your terminal:
npm is configured from the following sources, sorted by priority:
For those who may be unfamiliar or new to Nodejs, npm and nvm the user needs to be aware that it’s possible to have more then one version of Node on your system.
It’s also possible to have Node stored both locally and globally.
Using the built-in Node/npm tools to locate Node seems to make the most sense.
Источник
[coc.nvim] node is not executable (node installed by nvm) #856
sandangel commented Jun 9, 2019 •
Describe the bug
When installed with nvm, node when we first started the shell is a function defined in nvm scripts. So if we use executable to check, the error will be shown as above
Reproduce the bug
I think We should change the executable(‘node’) check to something else, because most of node users is using nvm to install node
The text was updated successfully, but these errors were encountered:
because most of node users is using nvm to install node
I can’t agree, since nvm sucks on many cases.
because most of node users is using nvm to install node
I can’t agree, since nvm sucks on many cases.
This personal opinion regarding nvm is irrelevant to the true fact mentioned by the OP.
Please reconsider providing a user-friendly feature for solving this annoying issue.
So how do I resolve this? I have just installed neovim and coc.nvim on a fresh ubuntu 16.04 system. Do I have to install nodejs?
just set the variable as suggested. nvm will have the node executable somewhere.
Cool! Had this same problem after removing the system’s node and replacing it by n node installation.
I also had the same problem. I’m using Fish shell with nvm (https://github.com/FabioAntunes/fish-nvm)
So, what I did was I just executed nvm_alias_command node and coc is working again
My linux pc got corrupted and decided to install ubuntu and had to re-install everything. As I download zsh I encountered this problem. May I ask where can I put this single line?
let g:coc_node_path = ‘/path/to/node’
do I just put that somewhere in coc.vim or am I wrong.
do I just put that somewhere in coc.vim or am I wrong.
put into your vimrc
make it work always: let g:coc_node_path = trim(system(‘which node’))
make it work always: let g:coc_node_path = trim(system(‘which node’))
system command would slow down your vim on startup significantly
Just add a zsh function to lazy load nvm before starting nvim/vim
worked out alright for me
NVM can’t be lazy loaded with this because NVM_BIN is unset until nvm is loaded
I still get a warning message when I open a new shell, but everything works.
Just add a zsh function to lazy load nvm before starting nvim/vim
worked out alright for me
This works but start nvim will freeze for 1-2s, but I think we don’t have another good solutions here. (anyway why load up node took so long?)
Either have fast prompt or fast nvim startup. I chose fast prompt.
Источник
Cannot install NodeJs: /usr/bin/env: node: No such file or directory
I’m trying to install nodeJs into my Ubuntu 14.04 in order to use GruntJs.
I’ve read about Ubuntu different way of doing it (issues?), so this is what I’ve done in order to install it:
Typing grunt after that I’ve got the error:
And trying again, and still getting the error, I’ve tried:
I’ve got this message:
I did try a cleanup just in case:
But nope, the error is still there: when I type grunt I still get /usr/bin/env: node: No such file or directory
19 Answers 19
Doing a symlink solves the issue:
The issue is not with the version of node. Instead, it is the way NodeJS is installed by default in Ubuntu. When running a Node application in Ubuntu you have to run nodejs somethign.js instead of node something.js
I think you should upgrade lastest node version
if you are using nvm node version manager, use this command to create a symlink:
and this may solve the problem
In my case, installing nodejs-legacy solved the issue.
And it will start working.
I’ve found this is often a misnaming error, if you install from a package manager you bin may be called nodejs so you just need to symlink it like so
If you already have nodejs installed (check with which nodejs ) and don’t want to install another package, you can, as root:
When I was using gulp i got this error.
/usr/bin/env: ‘node’: No such file or directory
This was removed by executing following command you have to keep in mind that /usr/bin directory has all permissions.
Using this command which node I found out the path, but to make the work easier you can run this command.
the above command will get the location of your node and create a link for you.
There are two solutions to this:
a) Set your PATH variable to include «/usr/local/bin»
b) Create a symlink to «/usr/bin» which is already in your PATH
Because of a conflict with another package, the executable from the Ubuntu repositories is called nodejs instead of node. Keep this in mind as you are running software.
So some other known tool (I don’t know what it does. While being known to ubuntu repositories, it is not installed by default in 16.04) occupies that namespace.
Would have been nice, if Ubuntu had offered an advice how to fix this ‘cleanly’, if not by doing by hand what otherwise the package would do. (a collision remains a collision. if+when it would occur)
For my case link did NOT work as follow
But you can open /usr/local/bin/lessc as root, and change the first line from node to nodejs.
Follow these commands to fix the problem.
Clean the entire NPM cache:
Install the latest stable version of Node.js:
Now the latest version of Node.js was installed. Check the version using:
For me the accepted answer did not yet work. I started off as suggested here:
After doing this I was getting the following error:
/usr/local/lib/node_modules/npm/bin/npm-cli.js:85 let notifier = require(‘update-notifier’)() ^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:374:25) at Object.Module._extensions..js (module.js:417:10) at Module.load (module.js:344:32) at Function.Module._load (module.js:301:12) at Function.Module.runMain (module.js:442:10) at startup (node.js:136:18) at node.js:966:3
Источник
Installed ShellWax 0.1.2 via Eclipse Marketplace. After restarting Eclipse I am presented with «Could not find node.js … make sure node.js is installed and that your PATH environment variable contains the location to the ‘node’ executable».
Thing is, node.js is installed and in the path. It has been installed via chocolatey and lives in «C:Program Filesnodejs». I can open a cmd window and execute «node» and «npm» from anywhere.
Am I doing something wrong?
Thanks!!
Which node version do you have ? I don’t have Windows handy so can’t test
locally.
…
On Fri, Jun 12, 2020 at 11:46 AM fzadow ***@***.***> wrote:
Installed ShellWax 0.1.2 via Eclipse Marketplace. After restarting Eclipse
I am presented with «Could not find node.js … make sure node.js is
installed and that your PATH environment variable contains the location to
the ‘node’ executable».
Thing is, node.js *is* installed and in the path. It has been installed
via chocolatey and lives in «C:Program Filesnodejs». I can open a cmd
window and execute «node» and «npm» from anywhere.
Am I doing something wrong?
Thanks!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#47>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMKRE7AJAWTUUZT4DCBA3RWHTNTANCNFSM4N4EEFKQ>
.
node 14.4.0
Anything else I can provide? Like I said, I can use node from anywhere, only ShellWax complains about not finding it.
So when you open cmd you can run node?
So when you open cmd you can run node?
Yes.
No reply from reported and without him not much could be done.
- Index
- » Newbie Corner
- » [SOLVED] Node: npm install package but no executable found
Pages: 1
#1 2016-11-26 19:21:08
- gleiton
- Member
- Registered: 2016-11-26
- Posts: 3
[SOLVED] Node: npm install package but no executable found
I have installed node tried to install express under default settings
So, according to https://wiki.archlinux.org/index.php/Node.js_ , I followed the step:
I uncommented prefix and set:
prefix=/home/gleiton/.node_modules
and added ~/.node_modules/bin to the $PATH
But after installing express
and opening a new terminal:
[gleiton@gleiton ~]$ express -h
bash: express: comando não encontrado
[gleiton@gleiton ~]$ whereis express
express:
[gleiton@gleiton ~]$ ls .node_modules/
etc lib
[gleiton@gleiton ~]$ npm list --depth=0
/home/gleiton
└── express@4.14.0
As we can see, there is no bin directory, neither in ~/.node_modules nor in /usr/lib/node_modules.
And, no executable known as «express»
Last edited by gleiton (2016-11-29 13:34:18)
#2 2016-11-27 12:15:58
- robg
- Member
- Registered: 2015-03-05
- Posts: 218
Re: [SOLVED] Node: npm install package but no executable found
Are you sure that setting the prefix took effect? Browsing through the wiki page you linked to, I suggest you try
npm -g install express --prefix /home/gleiton/.node_modules
and report back on whether that was successful.
#3 2016-11-28 15:58:53
- gleiton
- Member
- Registered: 2016-11-26
- Posts: 3
Re: [SOLVED] Node: npm install package but no executable found
@robg thanks for the tip. I chose setting prefix by npm config edit, and I’ve seen files were copied there.
Anyway I executed your command line, logged in again but nothing.
Files related to express are installed, but no command «express», and no «bin» directory.
$ find ~/.node_modules/ -type f -name express
(nothing shown)
#4 2016-11-28 20:50:36
- robg
- Member
- Registered: 2015-03-05
- Posts: 218
Re: [SOLVED] Node: npm install package but no executable found
I checked it out myself and you are right. However the solution to your problem is not far: If you check ~/.node_modules/lib/node_modules/express and have a look at the content of the Readme.md file in that folder you’ll notice that the command line utility for express is apparently in a separate package called «express-generator». In fact executing
npm -g install express-generator --prefix ~/.node_modules
did the trick for me.
#5 2016-11-29 13:10:49
- gleiton
- Member
- Registered: 2016-11-26
- Posts: 3
Re: [SOLVED] Node: npm install package but no executable found
Great! That worked for me too. Now there’s something in bin/ path.
$ find ~/.node_modules/ -type f -name express
/home/gleiton/.node_modules/lib/node_modules/express-generator/bin/express
$ find ~/.node_modules/ -type l -name express
/home/gleiton/.node_modules/bin/express
Maybe my book is outdated, but the documentation is clear. Reading the old Readme is always a good idea.
Thanks a lot @robg, I think I can put a «Solved» on this issue, with «perfect» rsrs.
Oleg
Привет. Застрял на «Подключите eslint к своему редактору, убедитесь что все работает. Скорее всего, понадобится поставить eslint глобально.».
Использую IDE PyCharm. В js файлах пишет «ESLint: specify Node.js interpreter». Захожу в настройки, чтоб определить интерпертатор, напротив Node interpreter пишет: «No executable found in $PATH». Найти его вручную тоже не удается.
3
0
Maksim Litvinov
Добрый день, Олег! Проверьте, установлен ли у вас Node.js. Выполните в терминале команду which node
. Возможно, эта страница документации поможет вам подключить линтер. Также, здесь есть информация о том, как сконфигурировать интерпретатор node.js
0
Oleg
Немного раскопал проблему…если пайчарм запустить из терминала, то ноду видит, линтер подключается, всё ок. А если запустить ide через ярлык, то она не видит каталог /src/local/ , где и находится нода. Может, есть идеи, почему так происходит?
0
Maksim Litvinov
Возможно, где-то нужно настроить значение переменной окружения $PATH и тогда при запуске через ярлык нода тоже будет доступна. К сожалению, не знаком с PyCharm. Попробуйте еще написать в наш слак чат, там общается много студентов и опытных разработчиков. Возможно, кто-то из них сталкивался с подобной проблемой и сможет быстрее подсказать вам
1
Хотя я следую советам:
- ‘node’ не распознается как внутренняя или внешняя команда, операционная программа или командный файл при использовании phonegap/cordova
- Node.js не распознает системный путь?
- ‘ant не распознается как внутренняя или внешняя команда…
У меня возникла странная проблема: Resume, хотя node path — это список в Path, он не находит node.
Workflow:
Microsoft Windows [Version 6.3.9600] //Running CMD on windows 8.1
(c) 2013 Microsoft Corporation. All rights reserved.
Я следил за предложениями в SO, добавляя переменную к переменным среды и отображая Ok в пути:
C:UsersmyUser>path
PATH=c:Program Files (x86)nodejs ; (...omitted...) //So folder is there
Следующая строка не будет выполнена
C:UsersmyUser>call jasmine-node spec
'node' is not recognized as an internal or external command,
operable program or batch file.
C:UsersmyUser>cd "c:Program Files (x86)nodejs" //So I move to the folder list before...
Но если я перейду в список папок в Path, то он будет работать нормально.
c:Program Files (x86)nodejs>call jasmine-node spec
> (...omitted...) //Exec OK.
c:Program Files (x86)nodejs>node
> //Exec OK. Waiting...
Кажется противоречивым.
Ответ 1
Каталог nodejs в вашем PATH
не распознается, потому что перед точкой с запятой существует пробел, поэтому Windows ищет каталог с пробелом в конце имени, которого не существует.
Ответ 2
Ошибка: ‘node’ не распознается как внутренняя или внешняя команда
Проблема может заключаться в том, что node не установлен на компьютере, на котором работает приложение.
Затем установите его и установите переменную среды для nodejs.
Или
Еще одной причиной может быть путь nodejs, который не задан в переменной среды.
Обратите внимание на следующее:
открыть панель управления → Система и безопасность → Система → Расширенные настройки системы → Переменные среды → Путь
путь nodejs должен быть доступен здесь.
Если недоступно, добавьте следующее:
C:Program Files (x86)nodejs
ИЛИ
C:Program Filesnodejs
Теперь перезапустите приложение, и ошибка была решена.
Ответ 3
; C:Program Filesnodejs
Слэш послеnodejsработал у меня
Ответ 4
Обычно переменные среды не действуют до тех пор, пока система Restart.
Я предлагаю System Restart
для всех тех, кто сталкивается с той же проблемой при выполнении чистой установки.
Это сработало для меня.
Ответ 5
Если вы сделали npm install jasmine-node -g
, вам просто нужно сделать jasmine-node spec
(no call
prefix).
Ответ 6
В Windows вам необходимо установить путь к папке node.js в системные переменные или пользовательские переменные.
1) откройте Панель управления → Система и безопасность → Система → Расширенные настройки системы → Переменные среды
2) в разделе «Пользовательские переменные» или «Системные переменные» найдите переменную PATH
и добавьте путь к папке node.js как значение. Обычно это C:Program Filesnodejs;
. Если переменная не существует, создайте ее.
3) Перезагрузите среду IDE или компьютер.
Полезно также добавить пути «npm» и «Git» как переменные, разделенные точкой с запятой.
Ответ 7
Если вы проверили свой PATH
и уверены, что путь для node
добавлен правильно, то вы, вероятно, столкнетесь с проблемой во время выполнения команд node
OR npm
с CLI, отличным от интерфейс командной строки по умолчанию для операционной системы (например, Git bash в Windows).
Странная часть состоит в том, что вы можете проверить node -v
и npm -v
в этих CLI, но по некоторым причинам они не очень хорошо работают с этими командами (особенно в сочетании с install
или update
).
Возможное решение
Попробуйте запустить node
с терминалом по умолчанию для вашей ОС.
Ответ 8
Я столкнулся с этой проблемой даже после добавления node.exe в PATH. Я не смог запустить команду node в случайных местах без запуска командной строки в качестве администратора.
Решение этой проблемы заключается в том, что вы должны предоставить полный доступ к этому файлу node.exe для разных типов пользователей. откройте свойства node.exe, перейдите на вкладки безопасности, проверьте все параметры безопасности для пользователя на локальном компьютере.
после этого вы сможете получить доступ к node.exe файлу из любого места.
Ответ 9
Ошибка:
node-is-not-recognized-as-an-internal-or-external-command
И следующее решение:
- Установите переменную среды
NODE_HOME
какC:Program Filesnodejs
- Откройте окно cmd и запустите:
cd "C:Program Filesnodejs"
npm install connect
npm install -g appium
Ответ 10
Это так же просто, как добавить расположение nodejs (C:Program Files (x86)nodejs
) в вашу переменную PATH
и перезапустить приложение с помощью «Запуск от имени администратора».