2 people reported
All time, since Sep 2.
Build panics on multi-byte characters
“🔴 最有害的一点：panic 发生在渲染诊断信息时 ⇒ 真正要报告的错误被吞掉，用户只看到 Panic in async function，无法定位。”
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/4237/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
Build panics in next-code-frame on multi-byte source characters. Turbopack next build dies with a Rust panic instead of printing the warning code frame, hiding the real diagnostic.
Is this your bug?
File my report- Where
- Turbopack build
- Error text
end byte index 93 is not a char boundary; it is inside '한' (bytes 91..94 of string)- Versions
- 16.3.4 to 16.3.5
- Platforms
- Windows
- How bad
- Breaks a normal workflow.