[atinux]

Written by an AI agent on behalf of @atinux. @atinux has not reviewed it yet.

Stacked on #1663 (client bundle summary), which is stacked on #1662 (quieter server build). Review those first; this PR only adds the last commit.

At the end of nuxt build there is no easy way to see which routes are prerendered, cached, client-only, redirected or proxied. Rules come from nuxt.config, from pages (defineRouteRules) and from modules, so the config file alone doesn't tell you.

What changed

• nuxt build prints a Route rules table (route, rules) after the client bundle summary.
• The rules are read from the Nitro instance (nitro:init hook) after the build. It is the only place that has page rules and module rules: nuxt.options.routeRules lacks page rules in production builds, and kit.tryUseNitro() returns nothing once the build has finished.
• Nitro's resolved rules are turned back into short labels: prerender, ssr: false, isr 600s, swr 3600s, cache: false, redirect → /x (307), proxy → url, cors, headers: <names> and middleware. Unknown keys are listed as they are.
• Works with Nitro 2 and Nitro 3. They resolve rules differently, so both are read:
  • Nitro 3 keeps only cache: { swr, maxAge } for swr.
  • Nitro 3 names the redirect code status, where Nitro 2 uses statusCode.
  • Nitro 3 leaves cors: {} without expanding it into headers.
• Nuxt's own entries are hidden: /__nuxt_error, the /** ssr: true default, the cache headers under app.buildAssetsDir, and the _payload.json copies of cached routes. Nuxt renames unnamed page segments to /:_2; they are shown as /* again.
• Routes are sorted and capped at 20 rows with +N more routes, like the chunk list in feat(build): summarise the client bundle at the end of nuxt build #1663. Nothing is printed when the app has no rules of its own.

Videos

Both apps use the same nuxt.config, with 7 route rules and experimental.inlineRouteRules, plus defineRouteRules({ prerender: true }) in pages/blog/[slug].vue. Before is #1663's head (2c6edf6), after is this branch. Recorded with asciinema in a 110×40 terminal and rendered with agg. Pauses are capped at 1.5s, so the clips run faster than the real builds.

Nitro 2 (Nuxt 4.6.2, Nitro 2.13.5)

Before	After

Nitro 3 (Nuxt 5.0.0-2610281032-c0c2b8f nightly, Nitro 3.0.260903-beta)

Before	After

Both builds exit 0 and print the same table:

Route rules  8 routes

Route         Rules
/             prerender
/admin/**     ssr: false
/api/**       cors, headers: x-api
/blog/*       prerender
/blog/**      swr 3600s
/old          redirect → /new (307)
/products/**  isr 600s
/proxy/**     proxy → https://example.com/**

The repo playground has no route rules, and its build prints no table.

Tests

test/unit/utils/route-rules.spec.ts checks the table against nitro.options.routeRules dumped from real Nitro 2 and Nitro 3 builds. It also covers the row cap and the empty case. The full suite passes (env -u NO_COLOR TERM=xterm-256color pnpm exec vitest run packages: 155 files, 2187 tests), as do eslint and tsc --noEmit.

Details and open questions

• In an interactive terminal, clack adds its own spacer between messages, so there are two gutter lines between blocks (visible in the videos). The client bundle summary above has the same gap. The non-TTY output is spaced correctly.
• The table doesn't say where each rule came from (config, page or module). Nuxt merges them before Nitro sees them, so this would need Nuxt to keep that information.
• This is a prototype, so it isn't behind a flag. It may need one (or --log-level) for apps with many rules.
• The timing line wraps at 110 columns; that comes from feat(build): quieter Nitro server build output #1662's phase names, not from this PR.

ELI5

After building, Nuxt now lists every page pattern that has special handling, such as "built ahead of time", "cached for an hour" or "sent to another URL". You can check it matches what you meant without reading through config files and pages.