Turbopack Error: Failed to write app endpoint /page

[Humoyun209]

Turbopack version: de6bc159
Next.js version: 0.0.0

Error message:

Failed to write app endpoint /page

Caused by:
- byte index 13 is not a char boundary; it is inside 'й' (bytes 12..14) of `Рабочий стол_frontend_vite_tsquery__next-internal_server_app_page_actions_74e668db`

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of endpoint_write_to_disk failed
- Execution of <AppEndpoint as Endpoint>::output failed
- Failed to write app endpoint /page
- Execution of all_server_paths failed
- Execution of server_path failed
- Execution of *FileContent::hash failed
- Execution of *AssetContent::file_content failed
- Execution of <SourceMapAsset as Asset>::content failed
- Execution of <EcmascriptBuildNodeEntryChunk as GenerateSourceMap>::generate_source_map failed
- Execution of *<Code as GenerateSourceMap>::generate_source_map failed
- Execution of EcmascriptBuildNodeEntryChunk::code failed
- Execution of <NodeJsChunkingContext as ChunkingContext>::chunk_path failed
- Execution of AssetIdent::output_name failed
- byte index 13 is not a char boundary; it is inside 'й' (bytes 12..14) of `Рабочий стол_frontend_vite_tsquery__next-internal_server_app_page_actions_74e668db`

[julienborgeon]

Hey!

It might be related to the project's file path. Turbopack still has a few rough edges with "non-ASCII" / Unicode characters in directory names, and the stack trace seems to reference Рабочий стол, which suggests the build tools could be trying to generate an output path from that string and... failing on a UTF-8 boundary.

A quick test could be to move the project to a folder with plain ASCII characters (e.g. C:\dev\next-app), then delete the .next directory and run npm install and npm run dev again.

If it still happens, running without Turbopack (next dev --no-turbo) might help narrow it down?

Hope this helps!