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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only specifying a major version in 'interpreter' option will not run node, as in 'node@10'.
It works fine if I specify the full version with 'node@10.14.1' but a full version number may vary from time to time or machine to machine and it has to be tracked in the config json instead of specifying just a major version, which is possible with nvm by running NODE_VERSION=10 ~/.nvm/nvm-exec [command] or nvm use 10 && [command].
It would be really helpful if this can be achieved.
How could we reproduce this issue?
Install nvm.
Create a json with, "interpreter": "node@10"
Run it with pm2.
Supporting information
--- Daemon -------------------------------------------------
pm2d version : 3.2.2
node version : 10.14.1
--- CLI ----------------------------------------------------
local pm2 : 3.2.2
node version : 10.14.1
--- System info --------------------------------------------
arch : x64
platform : linux
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What's going wrong?
Only specifying a major version in 'interpreter' option will not run node, as in 'node@10'.
It works fine if I specify the full version with 'node@10.14.1' but a full version number may vary from time to time or machine to machine and it has to be tracked in the config json instead of specifying just a major version, which is possible with nvm by running
NODE_VERSION=10 ~/.nvm/nvm-exec [command]
ornvm use 10 && [command]
.It would be really helpful if this can be achieved.
How could we reproduce this issue?
"interpreter": "node@10"
Supporting information
The text was updated successfully, but these errors were encountered: