Rank, 14 days: 3 on the Next.js sheet
4 people reported
All time, since Sep 14, including 1 thumbs-up on GitHub.
Hash links concatenate fragments
“Every subsequent hash navigation on that route keeps prepending: /#a#c, /#a#b#d after another reload, etc.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/next-js/issues/4192/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Hash links concatenate fragments after initial load with a hash. In production App Router builds, clicking a same-page <Link href="#b"> after a full load at /#a gives /#a#b.
Is this your bug?
File my report- Where
- next/link
- Versions
- 16.3.3 to 16.4.1
- Platforms
- Linux, Web, Windows
- How bad
- Breaks a normal workflow.
Not quite your bug?
Original reports3, newest first
- Same-page hash link doubles the hash (#a#a) after the page was loaded with a hashOn GitHub#101168
- App Router: hash fragments still concatenate (
/#a#b) after a full load at a fragment URL — initial-load path not covered by #93132On GitHub#99245 - next/link hash navigation concatenates fragments after an initial load with a hash (production only, hydration path — not covered by #93132)On GitHub#98644