@nuxt/kit incompatible with node 20
I am trying to get my nuxt project running on Node 20 using Nuxt 3.11.2 but I get the following error when I run
yarn install
:
Any tips to get around it?8 Replies
I opened this issue with more context: https://github.com/nuxt/nuxt/issues/26841
GitHub
Compatibility issues between @nuxt/kit and Node.20 Β· Issue #26841 Β·...
Environment Operating System: Darwin Node Version: v20.12.2 Nuxt Version: ^3.11.2 CLI Version: 3.11.1 Nitro Version: - Package Manager: yarn@1.22.22 Builder: - User Config: app, css, postcss, sourc...
Answered ππ»
I have a follow up question, perhaps we can chat here and then maune I can update my comments there.
I see what you're saying but I am not sure why it keeps pulling that older version. What can I do to force it to pull a newer version?
I've tried things like deleting my yarn.lock and node modules, using
npx nuxi upgrade --force
, but with no luck.
Perhaps it's even a third-party library now that I think about it... π€Check via npm why @nuxt/kit
I did, turns out
nuxt-proxy
relies on it in my case! At least now I know where to look, thanks!PS: you donβt need Nuxt proxy
The BEST way to proxy your API in Nuxt
https://youtu.be/J4E5uYz5AY8
Alexander Lichter
YouTube
The BEST way to proxy your API in Nuxt
β‘οΈ Proxying routes to your back-end or third party APIs is a common practice! Over the last two years, various strategies came up in Nuxt. But not all of them work equally will. To figure out which two strategies are the recommended ones, we have a look at the four most common strategies, their shortcomings and which ones I would recommend to us...
Right, I tried migrating away from it but with no luck just yet.
This is what I had:
This is what I currently have:
Not sure what's different, but I do get success codes in both cases - I just don't get back any json data anymore with the new method. Still investigating it on my end