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

macOS upgrade to Node 22 LTS #55600

Closed
outbackStack opened this issue Oct 30, 2024 · 5 comments
Closed

macOS upgrade to Node 22 LTS #55600

outbackStack opened this issue Oct 30, 2024 · 5 comments
Labels
wrong repo Issues that should be opened in another repository.

Comments

@outbackStack
Copy link

Version

v22.11.0

Platform

macOS 15.1

Subsystem

No response

What steps will reproduce the bug?

upgrade to node 22 from 20

➜ ~ nvm install 22
v22.11.0 is already installed.

restart terminal and it reverts back to node 20

➜ ~ node -v
v20.16.0

How often does it reproduce? Is there a required condition?

every restart of terminal

What is the expected behavior? Why is that the expected behavior?

should show node 22

What do you see instead?

node 20

Additional information

No response

@outbackStack outbackStack changed the title macOS Node 22 macOS upgrade to Node 22 Oct 30, 2024
@outbackStack outbackStack changed the title macOS upgrade to Node 22 macOS upgrade to Node 22 LTS Oct 30, 2024
@ghaneshmouthouvel
Copy link

Try nvm use 22 it will set your node to 22

@outbackStack
Copy link
Author

still no luck, it just revert to 20 after terminal restart...

Screenshot 2024-10-30 at 7 04 54 pm

@UlisesGascon
Copy link
Member

UlisesGascon commented Oct 30, 2024

Hey @outbackStack! Probably you need to change the default version used in nvm. Otherwise when you open a different terminal (or restart it) you get again the "old version".

You can do that by running nvm alias default 22.

Documentation

@outbackStack
Copy link
Author

thank you @UlisesGascon! that works! learn something new every day 😀

@UlisesGascon
Copy link
Member

UlisesGascon commented Oct 30, 2024

As this is solved now, I will close the issue.

@avivkeller avivkeller added the wrong repo Issues that should be opened in another repository. label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

4 participants