Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Next 16.1 breaks catch-all routes with no parameter name [9 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#87671•Fetched 2026-04-08 02:06:41
View on GitHub
Comments
9
Participants
3
Timeline
14
Reactions
0
Author
icoppicopp
Participants
icoppicoppicyJosephicyJosephwyattjohwyattjoh
Timeline (top)
commented ×9subscribed ×2issue_type_added ×1labeled ×1

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.1.0: Mon Oct 20 19:26:04 PDT 2025; root:xnu-12377.41.6~2/RELEASE_ARM64_T8122
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 22.20.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.1-canary.3 // Latest available version is detected (16.1.1-canary.3).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/icopp/catch-all-routes-with-no-parameter-name

To Reproduce

  1. Run next build

Current vs. Expected behavior

Expected behavior: The build succeeds, like it did in 16.0.0.

Actual behavior: The build errors out with Parameter names cannot be empty in route "route-path-here/[...]".

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.1.0: Mon Oct 20 19:26:04 PDT 2025; root:xnu-12377.41.6~2/RELEASE_ARM64_T8122
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 22.20.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.1-canary.3 // Latest available version is detected (16.1.1-canary.3).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Route Handlers

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed), next build (local)

Additional context

No response

extent analysis

TL;DR

The issue can likely be fixed by updating the route configuration to include a parameter name in the catch-all route.

Guidance

  • Review the code at https://github.com/icopp/catch-all-routes-with-no-parameter-name to identify the specific route causing the error.
  • Check the Next.js documentation for the correct syntax for catch-all routes with parameter names.
  • Update the route configuration to include a parameter name, for example, changing "route-path-here/[...]" to "route-path-here/[...param]".
  • Verify that the build succeeds after updating the route configuration.

Example

No code snippet is provided as the issue does not include the specific code that needs to be updated.

Notes

The issue seems to be related to a change in Next.js version 16.1.1-canary.3, which now requires parameter names in catch-all routes.

Recommendation

Apply workaround: Update the route configuration to include a parameter name, as this is a required change in the latest version of Next.js.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#tokenizer error#prompt formatting#chain error#conversation history#tool integration

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Next 16.1 breaks catch-all routes with no parameter name [9 comments, 3 participants]