Today, we’re announcing Netlify’s participation in the OpenNext project. The goal of the OpenNext project is to make sure you can deploy Next.js sites to any cloud platform that best fits developers’ and end users’ needs. We are moving our open-source Next.js adapter for Netlify to the OpenNext GitHub organization and will start collaborating across providers, such as Cloudflare and SST, to make sure Next.js runs well everywhere.
At Netlify, we’ve always believed in developing with core platform primitives that align with the web platform. This development approach brings you unparalleled portability on the most comprehensive platform for accelerating time to market and improving end user experience on the web. We think the OpenNext project is a great way to create an open-source forum for collaborating across competitors and cloud platforms to increase the portability and flexibility of Next.js across different providers—benefitting both developers and end users.
Our team at Netlify knows what it takes to make Next.js run with full support in an edge-accelerated front-end cloud environment and has long been the only other place—outside of Vercel—with full support for all Next.js features, including on-demand Incremental Static Regeneration (ISR), Partial Prerendering (PPR), and edge middleware. These features are only possible on Netlify today because of the high-performing and scalable Next.js adapter (formerly known as the Next.js runtime) enabling these features on Netlify’s platform.
I’m really proud of the work our Frameworks team has done, not just building out our adapter for Next.js but also building out the extensive test suites required to ensure everything keeps working across Next.js releases and updates for our Netlify users and their customers.
Are there any changes to my current Next.js site?
With the Next.js adapter moving to the OpenNext organization, you might have questions on how it affects your Next.js sites on Netlify. For all Netlify Next.js users, nothing will change today.
Once we have fully migrated the OpenNext Netlify adapter, for most sites on Netlify that automatically install the Next.js adapter, nothing will change. Your Next.js site will require no changes and will support all the latest Next.js features.
If your site is manually installing our Next.js runtime v5 package, you will need to update the package name or you won’t get new updates. We will update the Netlify Next.js documentation with more information when the OpenNext Netlify adapter is ready. At that time, we’ll reach out to users manually installing the package.
If you’re still on an older version of the Next.js runtime (v4 or older), it’s important to note that these versions do not support the new Next.js App Router, automatic fine-grained caching, on-demand and time-based revalidation, and image optimization with the Netlify Image CDN by default. To use these features, the Netlify Next.js documentation can assist you in migrating to the latest version.
We look forward to collaborating with everyone involved in the OpenNext project—striving to build a better web together.
Try out Next.js today on Netlify using our Next.js starter template.
