Next.js compatibility

How this works

The Next.js deploy test suite runs nightly against vinext. The GitHub Actions workflow aggregates each test file's pass / fail / skip counts and POSTs the results to this app's ingest endpoint, where they are stored in a D1 database. Each suite is classified by which router(s) its fixture exercises (App Router, Pages Router, or both — "mixed"). Mixed suites are counted toward both router pass rates, so adding the App and Pages numbers exceeds the total. Suites without an on-disk fixture (config / build / edge-runtime tests) are bucketed under "Other". Results are keyed by kind so additional suites (e.g. ecosystem apps, Vitest) can be added later without schema changes.

The supported pass rate excludes suites classified as deferred, specific to the Next.js compiler, or awaiting equivalent Vite coverage. The overall pass rate retains their raw results. Both rates exclude tests skipped by Next.js itself. Support classifications are joined when this page is read, so they apply consistently to historical runs without rewriting stored results.

Router and support classifications are both applied at read time. Reclassifying a suite therefore updates its supported rate, color, and router bucket across every historical run while leaving the stored raw results and overall rate unchanged.