next-queryCompatibility
What works on Next.js 15 and 16, and what runs where.
Next.js
Each version below runs the real playground app in CI, in both next dev and the production build (next build and next start). The smoke test checks caching, revalidation by tag (for a tagged native fetch and for query()) and the panel's server actions.
| Next.js | Status |
|---|---|
| 15.0.x (15.0.4) | Tested in CI, dev and production |
| 15.5 | Tested in CI, dev and production |
| 16.0 | Tested in CI, dev and production |
| latest | Tested in CI, dev and production |
| canary | Tested on every push to main, every pull request and weekly, non-blocking |
Canary breaking is a heads-up, not a blocker: it runs on every push to main and every pull request, plus every Monday, so changes show up before users see them.
Everything else
| React | 19 |
| Router | App Router only. The Pages Router is not supported. |
| Node | 22.18 or newer, to develop this repo |
What it is built on
Tags are Next's own cache tags, applied to your native fetch through next.tags, and revalidate() calls revalidateTag. query() is built on unstable_cache. Nothing uses 'use cache' and nothing needs cacheComponents, so it works whether or not you enable them in your app. The panel lists only fetches that go through the fetch cache, so a fetch inside 'use cache' is not listed.