Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix Support route groups in Middleware matcher config

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…

Fix Action

Fix / Workaround

Currently, the middleware matcher config does not support route groups. For example, matcher: "/(dashboard)/(.)" does not match routes inside the (dashboard) route group. The workaround is using "/:path" which is too broad. Requesting native route group support in matcher patterns. Next.js 14.x.

RAW_BUFFERClick to expand / collapse

Currently, the middleware matcher config does not support route groups. For example, matcher: "/(dashboard)/(.)" does not match routes inside the (dashboard) route group. The workaround is using "/:path" which is too broad. Requesting native route group support in matcher patterns. Next.js 14.x.

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…
#agent execution#callback error#memory management#API rate limit#retriever error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING