Applicable to:
- Plesk
Symptoms
Unable to start a Node.js application in Plesk using Run Script option in Domains > example.com > Node.js > Run Script
CONFIG_TEXT: start
> app-service-hello-world@0.0.1 start /var/www/vhosts/example.com/httpdocs
> node index.js
npm WARN lifecycle npm is using /opt/plesk/node/8/bin/node but there is no node binary in the current PATH. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.
sh: node: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
[...]
Cause
node binary was not found by npm since it is missing on the specified PATH
Resolution
Add scripts-prepend-node-path=true into .npmrc file in Node.js Application Root folder.
-
Go to Domains > example.com > Node.js
-
Click open next to Application Root
-
Using File Manager add
scripts-prepend-node-path=trueinto.npmrcfile. Create the file if it does not exist.
Or add the variable into a global npm config file
-
Connect to the server over SSH
-
Execute the following to configure the corresponding Node.js version. The example below shown for Node.js 8:
Create the
/etcdirectory in/opt/plesk/node/8/:# mkdir /opt/plesk/node/8/etc/
Add the following variable to the
nmprcfile:# echo "scripts-prepend-node-path=true" >> /opt/plesk/node/8/etc/npmrc
Comments
2 comments
Nelson Leiva I don't have any npmrc file, and the "etc" directory doesn't exist. Do you want us to create it? Because if I create it, it seems to work.
Hi Paolo Gabrielli, Thank you for noticing that! The article was updated accordingly.
Please sign in to leave a comment.