-
Notifications
You must be signed in to change notification settings - Fork 29
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
Update frontend tooling to use Node 20 #273
Conversation
OK this may be blocked by Vercel not supporting Node 20 yet. https://vercel.com/docs/functions/serverless-functions/runtimes/node-js#node.js-version |
Ok. We might be able to use Node 20 now in Vercel. |
e862572
to
c70d5d3
Compare
OK not sure here, will have to review again later. Changing Vercel to Node 20 was breaking all the builds so I have just turned it back off for now.
|
Oops, I didn't see that we don't use Node 20 yet. I updated the RTD config to use Node 20 in #284 , builds OK (with some warnings) but I assume we'll want to update it anyway. |
I think that's fine, it's just Vercel taking a bit to make their Node 20 support official. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lb- 👍
I'm doing major spring cleaning on sphinx-wagtail-theme today so I will merge this now.
Ensure we are on the latest LTS of Node for frontend tooling.
See wagtail/wagtail#11141 (Wagtail core update)