You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, in particular for #1563 , we adopted a polyfill for now to support the transition from Node 22 -> 24 since URLPattern had not been backported at this time, and serverless hosting providers are still working on support for Node24, so this didn't feel like the right time to force the cutover.
Technical Design
Should bump to >= 24.12.0 since that is the first LTS with stable TypeScript type-stripping support
Motivation
As Node 24 moves into Active LTS, Node 22 will go out of maintenance by this time next years

https://nodejs.org/en/about/previous-releases
However, in particular for #1563 , we adopted a polyfill for now to support the transition from Node 22 -> 24 since
URLPatternhad not been backported at this time, and serverless hosting providers are still working on support for Node24, so this didn't feel like the right time to force the cutover.Technical Design
URLPatternpolyfillURLPatternfor extracting props per feat(cli): #882 dynamic SSR and API routing #1563Additional Context
We should at least make sure to do this prior to the 1.0 release since this would be a breaking change.
Also, for Netlify (at least right now) an environment variable is required for Node 24 support - #1533 (comment)