Next.js compatibility
Results from the Next.js deploy test suite, run against vinext. Each dot below is one test file. Hover for details. The line chart tracks overall pass rate across runs.
Latest run: May 24, 2026, 3:36 AM UTC · Next.js v16.2.6 · vinext refs/heads/main
By router
Test files and trend
801 files in the latest run · last 11 runsTest files
Compatibility over time
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.
Per-router trend lines use the latest classification snapshot, so reclassifying a suite (when the Next.js ref bumps, or when the heuristic improves) updates how it appears across every historical run. The aggregate "All" line is unaffected.
View deploy suite runs