Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying only major version for nvm in 'interpreter' option #4048

Closed
windware-ono opened this issue Nov 30, 2018 · 3 comments
Closed

Specifying only major version for nvm in 'interpreter' option #4048

windware-ono opened this issue Nov 30, 2018 · 3 comments
Labels

Comments

@windware-ono
Copy link

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] or nvm use 10 && [command].

It would be really helpful if this can be achieved.

How could we reproduce this issue?

  1. Install nvm.
  2. Create a json with, "interpreter": "node@10"
  3. 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
@stale
Copy link

stale bot commented May 24, 2020

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.

@stale stale bot added the stale label May 24, 2020
@windware-ono
Copy link
Author

Anyone wants to take a look at this?

@stale stale bot removed the stale label May 30, 2020
@stale
Copy link

stale bot commented Jun 30, 2020

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.

@stale stale bot added the stale label Jun 30, 2020
@stale stale bot closed this as completed Jul 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant