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
Unable to start DDEV with nodejs_version: 18
(upstream problem, fix with nodejs 16)
#4614
Comments
Strangely I can't reproduce this on my Apple Silicon Mac. One of my coworkers pointed out there's breaking npm changes in the latest nodejs release :( |
Looks like |
I cannot replicate a failure with |
I can confirm that the last Github Action job that passed without error was using:
So this does seem to be caused by npm 18.14.0 |
I can replicate it locally now:
|
Looks like I need to copy the fix from #4610 to the Dockerfile. |
Given that node intentionally added breaking changes in an LTS release, I think ddev should consider pinning the minor version, or at least allowing the minor to be specified in Normally, I'd also want to report this upstream... but they clearly knew there were breaking changes and released it anyways: nodejs/node#46396 |
I'm pretty sure this was already solved in I hope you'll try HEAD, |
@rfay do you expect to roll a new release to fix this soon? If not, that's fine, but then we'll probably invest some time in working on jonaseberle/github-action-setup-ddev#15. |
v1.21.5 is planned to be released on March 5. Do you think it needs some kind of emergency patch release? |
I think there might be a possible workaround that could be implemented with a |
@deviantintegral I'm not even sure that they make packages available for non-current versions, but they may. Many debian package providers don't provide the old ones. We could probably figure out how to move to nvm-only. But wow, this was sure nasty. Thanks for tracking down the issue. I was really annoyed when all the tests broke at once. |
I was just able to replicate on my Mac after wiping my docker images completely - I must have had some dangling docker images I thought I'd removed. This is certainly broken for node 18. Node 16 works correctly. As far as a hotfix goes, I guess it depends how many users you expect to be on node 18? |
For anyone else searching: The files are From our read, because there's no conditional on the line that errors there isn't a way to use that file to fix this. |
I'll take a look this afternoon and see if I can see a workaround. |
It looks like we don't have any hard node 18 dependencies so we can actually downgrade to 16 for now. Given there's only a few in this issue I'm guessing the majority of ddev users are on 16 and not 18. |
nodejs_version: 18
I don't see a way to use a .ddev/web-build/pre.Dockerfile.npm and solve this. So the options I can think of are these, given a release is scheduled for the first Sunday in March, March 6:
|
Added a 4th option to the possibilities in #4614 (comment) |
nodejs_version: 18
nodejs_version: 18
(upstream problem, fix with nodejs 16)
I'd probably support 3 or 4. |
I've been running HEAD since Monday and it's been fine. I would lean towards towards #4. Make sure that the release notes indicate this is all changes and reflects the upcoming release, and then if you get feedback about bugs you could roll a hotfix only release but you'd have the benefit of the bug reports for the March release. |
Prerelease fixing this issue is available https://github.com/drud/ddev/releases/tag/v1.21.5-alpha1 |
Closing, leaving it pinned. This had already been fixed in #4610 |
Is there an existing issue for this?
Run a Diagnostic and Paste Link Here
No response
Expected Behavior
For startup to succeed without fail.
Actual Behavior
Steps To Reproduce
ubuntu-latest
- Ubuntu 22.04In config.yaml:
Anything else?
This job used to succeed four days ago and started failing three days ago. I can confirm this in GIthub Actions as well as my local machine.
The text was updated successfully, but these errors were encountered: