Repository navigation
Conversation
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 8, 2026 08:33
18602f5 to
38d07fe
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 8, 2026 08:35
c7c87ac to
0b40141
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 8, 2026 08:45
38d07fe to
5ab9fa8
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 8, 2026 08:47
0b40141 to
7282bdf
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 8, 2026 08:48
5ab9fa8 to
aba7cd5
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 8, 2026 08:50
7282bdf to
2951767
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 8, 2026 08:57
aba7cd5 to
71dc0ba
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 8, 2026 08:58
2951767 to
b3afdc7
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 8, 2026 09:14
71dc0ba to
2c6edf6
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
3 times, most recently
from
November 8, 2026 09:23
ba511a6 to
0e69230
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 9, 2026 22:38
2c6edf6 to
893a812
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 9, 2026 22:40
0e69230 to
3738578
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 10, 2026 11:36
893a812 to
eb95914
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 10, 2026 11:38
3738578 to
128bc02
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 10, 2026 11:42
eb95914 to
a696a61
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 10, 2026 11:44
128bc02 to
8744da0
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 10, 2026 11:48
a696a61 to
b474ee8
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 10, 2026 11:50
2f6be04 to
830cd25
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 10:35
b474ee8 to
3c02b79
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
2 times, most recently
from
November 12, 2026 10:40
efa82d6 to
75d9178
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 10:57
3c02b79 to
2a97d04
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 11:00
75d9178 to
faa61df
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 11:12
2a97d04 to
d23c61a
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 11:16
faa61df to
9822096
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 13:33
d23c61a to
3aaf940
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 13:36
9822096 to
66f97a4
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 13:38
3aaf940 to
40d4436
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 14:26
e3eeab1 to
6b7ed3a
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 14:33
4e24abb to
0ce7b03
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 14:37
6b7ed3a to
08b3d3e
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 14:40
0ce7b03 to
f2ad3b8
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 14:59
08b3d3e to
f99d469
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:02
f2ad3b8 to
0bd801f
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 15:08
f99d469 to
bbacef2
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:11
0bd801f to
44ff09a
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 15:25
bbacef2 to
02160aa
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:29
44ff09a to
2311326
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
2 times, most recently
from
November 12, 2026 15:38
d216d21 to
bffb11d
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
2 times, most recently
from
November 12, 2026 15:42
743ec0f to
c41c0f4
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 15:43
bffb11d to
83cbeed
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:46
c41c0f4 to
0286b5c
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 15:48
83cbeed to
22a8122
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:51
0286b5c to
cc08408
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 15:55
22a8122 to
f258062
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 15:58
cc08408 to
150f9be
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 16:02
f258062 to
a305009
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 16:06
150f9be to
b19c417
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 12, 2026 16:13
a305009 to
b0d4a28
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 12, 2026 16:16
b19c417 to
987ed48
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
from
November 13, 2026 00:06
b0d4a28 to
2c0c31d
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 13, 2026 00:10
987ed48 to
0d00688
Compare
atinux
force-pushed
the
feat/client-bundle-summary
branch
2 times, most recently
from
November 16, 2026 12:01
46dc948 to
9f2ae96
Compare
atinux
force-pushed
the
feat/build-route-rules
branch
from
November 16, 2026 12:05
0d00688 to
edf8438
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #1663 (client bundle summary), which is stacked on #1662 (quieter server build). Review those first; this PR adds the last two commits: the route rules table, and a fix for the spacing between the summary blocks.
At the end of
nuxt buildthere is no easy way to see which routes are prerendered, cached, client-only, redirected or proxied. Rules come fromnuxt.config, from pages (defineRouteRules) and from modules, so the config file alone doesn't tell you.What changed
nuxt buildprints a Route rules table (route, rules) after the client bundle summary.nitro:inithook) after the build. It is the only place that has page rules and module rules:nuxt.options.routeRuleslacks page rules in production builds, andkit.tryUseNitro()returns nothing once the build has finished.prerender,ssr: false,isr 600s,swr 3600s,cache: false,redirect → /x (307),proxy → url,cors,headers: <names>andmiddleware. Unknown keys are listed as they are.cache: { swr, maxAge }forswr.status, where Nitro 2 usesstatusCode.cors: {}without expanding it into headers./__nuxt_error, the/**ssr: truedefault, everything underapp.buildAssetsDir, the cache header Nitro adds for eachpublicAssetsdirectory with amaxAge(such as a module's/_og-static-fonts/**), and the_payload.jsoncopies of cached routes. Nuxt renames unnamed page segments to/:_2; they are shown as/*again.+N more. Redirects are grouped onredirectalone, since each has its own target. Past 20 groups, the rest are counted (+N more rules on M routes).…, so the second column stays visible. Rows fit inside clack's gutter.isr: { expiration, allowQuery }shows its expiration (isr 3600s), andprerender: falseis left out next to a redirect or proxy.Videos
Both apps use the same
nuxt.config, with 7 route rules andexperimental.inlineRouteRules, plusdefineRouteRules({ prerender: true })inpages/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)
Nitro 3 (Nuxt 5.0.0-2610281032-c0c2b8f nightly, Nitro 3.0.260903-beta)
Both builds exit 0 and print the same table:
The repo playground has no route rules, and its build prints no table.
A large app: nuxt.com
A real
nuxt buildof nuxt/nuxt.com (15c1ea3) with this branch, in a 110-column terminal: exit 0, 3m 27s. Its build has 382 route rules: 303 redirects (mostly old/docs/2.xpaths), 52 ISR,ssr: false, header and proxy rules, and module-added asset rules. Once Nuxt's own rules are hidden, the 352 routes that remain fit in 16 rows grouped by rule:The first version of this PR listed 20 alphabetical routes with no rules visible there. Two Vercel BotID proxy routes of about 75 characters widened the Route column past the terminal, and redirects and asset routes filled the rows.
One blank line between the summary blocks
The second commit fixes the double gap. In a terminal, clack writes a
│spacer row before every message. The client bundle summary and the route rules table each also ended with a newline of their own, so the gap between blocks was two gutter rows. The gap before the client summary was also two rows, fromblankLineBefore()plus clack's spacer.New
logBlock()inutils/logger.tsleaves the spacing to clack in a terminal. In redirected output it writes the blank lines itself, starting stdout spacing tracking so a block right after another one does not add a second blank line. Both summary blocks inbuild.tsnow use it. Redirected output is byte-for-byte the same as before around both blocks.test/unit/utils/logger.spec.tschecks both presentations, and its terminal case fails on the old spacing.Tests
test/unit/utils/route-rules.spec.tschecks the table againstnitro.options.routeRulesdumped from real Nitro 2 and Nitro 3 builds and against nuxt.com's rule shapes. It also covers the grouped layout, the cap on groups, 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 andtsc --noEmit.Details and open questions
--log-level) for apps with many rules.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.