Skip to content

Next.js Ecosystem Working Group

Purpose

The Next.js Ecosystem Working Group ("the WG") is a forum for coordination between the Next.js team at Vercel and Next.js ecosystem partners including but not limited to deployment platforms. Its purpose is to discuss upcoming changes to Next.js that may affect members, collect feedback, and coordinate cross-platform issues.

It is not a decision-making body over the direction of Next.js itself; design decisions, feature priorities, and release timelines remain with the Next.js team. Next.js is an opinionated framework, and we think about platform support through functional fidelity and performance fidelity. The WG is how we hold ourselves accountable to giving platforms the time and tools to get there. The scope is currently focused on deployment adapters and platform integration, but may expand to other areas of the ecosystem over time.

Membership

The WG includes engineers from the Next.js team, platform partners, and adapter maintainers. New members can join by request. Current member organizations include:

  • Vercel (Next.js team)
  • Netlify
  • Cloudflare
  • Google Cloud
  • AWS Amplify
  • OpenNext

If you want to participate, open an issue on the adapters-wg repository.

Operations

The WG meets on a recurring cadence. Meeting summaries are published publicly in the working group repository so the broader community can follow along. WG members reserve the right to omit or redact information from these summaries.

The WG maintains a dedicated private chat room for asynchronous discussion between calls.

Commitments

This is a working relationship, not a legal contract. The commitments below reflect how we intend to operate: the kind of things you'd expect from people who are building together and want it to work. When specifics aren't defined, the expectation is that we'll work it out together.

Partners will share timely feedback, including suggested changes to Next.js itself to accommodate their needs. Partners maintaining a verified adapter are expected to keep it passing the compatibility test suite as new releases ship.

The Next.js team will consider that feedback seriously and, where it isn't adopted, explain the reasoning to the WG.

In addition, the Next.js team commits to:

Early notice. Changes to the Adapter API or to framework behavior that affects deployment will be communicated through the WG before they ship. The lead time scales with the scope of the change: routine updates get standard pre-release notice, while changes that require significant infrastructure work from platforms (new runtime models, major caching changes, new deployment primitives) will be shared months in advance.

Coordinated testing. Before major releases and new features, the Next.js team will work with platform teams to run the compatibility test suite against their adapters and flag issues early.

Adapter breakage does not block a framework release. We will surface problems and give adapter teams time to respond before and after release, but the framework ships on its own schedule.

Documentation of deployment requirements. When Next.js features require unusual infrastructure that platforms generally cannot meet out of the box, the Next.js team will document those requirements and provide a reference implementation or describe a reference architecture. See Deploying to Platforms.

APIs for functional parity. The Next.js team commits to providing the APIs that adapter authors need to achieve full feature support on their platforms. The commitment is not only advance notice of changes, it's giving adapter authors the tools to implement them.

Direct support. When the adapter contract needs updating, the Next.js team will work directly with adapter teams to ensure they have what they need before features ship. This includes early access to API changes during the RFC and release candidate process.

Disagreements

If a WG member disagrees with an API change, a test suite update, or any other decision that affects their adapter, the right move is to raise it: in the WG chat, on a call, or as an issue in the repository. We'll discuss it. The Next.js team retains final decision-making authority over the framework, but we commit to hearing concerns, explaining our reasoning, and looking for workable solutions before shipping changes that materially affect adapter authors.