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

Built in cross-platform nodejs version manager #37109

Closed
Milo123459 opened this issue Jan 28, 2021 · 10 comments
Closed

Built in cross-platform nodejs version manager #37109

Milo123459 opened this issue Jan 28, 2021 · 10 comments
Labels
feature request Issues that request new features to be added to Node.js. stale

Comments

@Milo123459
Copy link

Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.
No.
Describe the solution you'd like
Please describe the desired behavior.
node update command. Updates NodeJS whilst still keeping global modules installed. Has to be cross-platform.
Kinda like rustup, but, for NodeJS & cross platform
Describe alternatives you've considered
Please describe alternative solutions or features you have considered.
nvm-windows except it breaks and make you re-install global packages.

@targos targos added the feature request Issues that request new features to be added to Node.js. label Jan 31, 2021
@theoludwig
Copy link
Contributor

I'm definitely +1 for this, maybe something similar to deno upgrade (see: https://deno.land/manual/getting_started/installation#updating).

Currently you can achieve this with nvm with this sort of command: nvm install 'lts/*' --reinstall-packages-from=current
It installs the latest LTS version of Node.js but it would be better if Node.js could have this thing builtin.

@github-actions
Copy link
Contributor

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

@github-actions github-actions bot added the stale label Mar 24, 2022
@theoludwig
Copy link
Contributor

This feature might still be relevant.

@bnoordhuis
Copy link
Member

This wouldn't be so difficult to implement for node itself, conceptually, at least. It's a single binary, like deno. The hard problem is updating npm.

@targos targos moved this to Pending Triage in Node.js feature requests Mar 26, 2022
@targos targos moved this from Pending Triage to Stale in Node.js feature requests Mar 26, 2022
@github-actions github-actions bot removed the stale label Mar 29, 2022
@github-actions
Copy link
Contributor

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

@github-actions github-actions bot added the stale label Sep 26, 2022
@Milo123459
Copy link
Author

Still relevant

@github-actions github-actions bot removed the stale label Sep 27, 2022
@targos targos moved this to Pending Triage in Node.js feature requests Oct 22, 2022
@github-actions
Copy link
Contributor

There has been no activity on this feature request for 5 months and it is unlikely to be implemented. It will be closed 6 months after the last non-automated comment.

For more information on how the project manages feature requests, please consult the feature request management document.

@github-actions github-actions bot added the stale label Mar 27, 2023
@theoludwig
Copy link
Contributor

Possible to disable Stale bot feature? 😅

Is an inactive issue no longer an issue?
I might be missing something, but is a stale bot really useful? What problem does it solve?
Are humans not capable to close issues when they are no longer relevant?
There are many repos on GitHub that use a stale bot but why, what does it bring?

(feel free to hide this comment as it is not relevant to this issue)

@bnoordhuis
Copy link
Member

It gained zero traction in the 2 years it's been open so I think it's only proper to let it die off. I'll go ahead and close this.

Are humans not capable to close issues when they are no longer relevant?

That's what I'm doing but, in general, at a project of node's size, the answer is 'no'. Turn on email notifications for all issues for a while, I dare you. :-)

@bnoordhuis bnoordhuis closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2023
@bnoordhuis
Copy link
Member

Also, this issue and #46409 are duplicates. That issue has a lot more discussion but didn't reach any real conclusion either.

(And I made the exact same point there that I made here. At least I'm consistent.)

@targos targos moved this from Pending Triage to Stale in Node.js feature requests Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issues that request new features to be added to Node.js. stale
Projects
None yet
Development

No branches or pull requests

5 participants
@bnoordhuis @targos @theoludwig @Milo123459 and others