-
-
Notifications
You must be signed in to change notification settings - Fork 579
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
How do I switch from nvm to nodejs_version
#6204
Comments
If you use
So does
fix this for you? |
|
You did something wrong there and were trying to execute with the PATH on the host.
You can easily After you've done that, a |
nodejs_version
not respectednodejs_version
|
Sounds like you already did it. You can use You can |
|
That means that you haven't deleted .nvm I guess.
and then you'll see that it's there. |
Oh sorry! You'll need to |
A different technique from https://ddev.readthedocs.io/en/stable/users/usage/commands/#nvm # Reset Node.js to `nodejs_version`
ddev nvm alias default system |
You were right, there was an .nvm there, so I
So I'm thinking I need to restart my machine. If that doesn't do it, I'll try @stasadev's suggestion. |
I'm able to reproduce your result. I guess the reason is that DDEV is finding your NVM and linking it on start. Please try in container:
Then That did it for me. We'll need a hint about this in the docs, probably in the nodejs_version doc, want to try your hand at that by clicking the pencil on the docs page? |
I think @stasadev 's solution in #6204 (comment)
is probably the best. Weird that that's not in the |
And thanks so much for your support for DDEV via GitHub Sponsors @syzygy333 . They don't give out email addrs, but would love to have you sign up for the DDEV newsletter at https://ddev.com/newsletter to keep in touch. (Also your github profile link to https://www.oomphinc.com/people/bhogue/ seems to be out of date/404) |
This did it! Finally!
Your speedy help was exceptional. Thanks so much. I'd be glad to contribute to the docs. (Also, thank you, I'll update my profile link.) |
See thread: ddev#6204
…#6207) [skip ci] Co-authored-by: Randy Fay <randy@randyfay.com>
Preliminary checklist
ddev debug test
to include output belowOutput of
ddev debug test
Expand `ddev debug test` diagnostic information
Expected Behavior
I have an existing project with a config file that used
post-start
hooks that in turn usednvm
to install node 14.I am trying to update my project's dependencies and, as part of this, updated ddev's config file to instead use
nodejs_version: "18"
and removed the aforementionedpost-start
hooks.I expected that I could remove old
post-start
hooks that usednvm
to install node 14, and switch to usingnodejs_version
to install node 18.Actual Behavior
Actual behavior is ... essentially nothing.
After I made this change, I powered off ddev, restarted
colima
, and restarted ddev. I randdev exec node -v
and it showedv14.21.3
. So I randdev clean <name>
and restarted everything again. Stillv14.21.3
. So then I randdev debug refresh
. I was hopeful because I saw this in the output:=> [web 6/7] RUN n install 18 && ln -sf 10.4s
. But, alas,ddev exec node -v
still showedv14.21.3
. Grasping at straws, I randocker buildx prune -a
and restarted everything once again. Stillv14.21.3
. Then I triedcolima prune
. Stillv14.21.3
.I am using the latest versions of ddev (1.23.1) and colima (0.6.8).
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: