1 person reported
All time, since Aug 25.
Non-Latin-1 route group names crash
“Error [InvalidCharacterError]: Invalid character”
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/4356/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
Non-Latin-1 route group names crash with InvalidCharacterError. Opening a page under a group like app/(안녕) returns 500 in next dev and fails prerendering in next build.
Is this your bug?
File my report- Where
- App Router routing
- Error text
Error [InvalidCharacterError]: Invalid character- Versions
- 16.3.3
- Platforms
- Windows
- How bad
- Stops work: a core feature can't be used. Most reports say it used to work.
Original reports3, newest first
- Route groups / segments with non-Latin-1 characters crash with
InvalidCharacterError: Invalid character(regression from Next 15)On GitHub#97890 - Route groups / segments with non-Latin-1 characters crash with
InvalidCharacterError: Invalid character(regression from Next 15)On GitHub#97886 - Route groups / segments with non-Latin-1 characters crash with
InvalidCharacterError: Invalid character(regression from Next 15)On GitHub#97883