You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
panic(main thread): Expected pretty file path to have only forward slashes, got 'E:\github\webgpu-2024\z2024-test\node_modules\localts\shader\render.wgsl'
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:
How can we reproduce the crash?
PS E:\github\webgpu-2024\z2024-test> bun build .\test.ts --outdir .\dist\
Bun v1.1.10 (5102a94) Windows x64
Args: "C:\Users\hjjls.bun\bin\bun.exe" "build" ".\test.ts" "--outdir" ".\dist"
Features: tsconfig(4)
Elapsed: 468ms | User: 31ms | Sys: 46ms
RSS: 51.90MB | Peak: 51.90MB | Commit: 111.23MB | Faults: 12888
panic(main thread): Expected pretty file path to have only forward slashes, got 'E:\github\webgpu-2024\z2024-test\node_modules\localts\shader\render.wgsl'
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:
https://bun.report/1.1.10/wb15102a94AgggggEqzk6V+g6oTgtn5Py1p5V+mojCwh4nCshoyFqn4BiiJo3ht+CA0eNoVxDEOwjAMBdCreOtCEaqY2HsLSyhtfpNKJo5il1BOj3jDmz8VqyNSbXA/adsFVINncqUc3iAtctKmrYcWySRYhl0oqdMwPzjtno+FO5ZUj3G6TXf+/h8d5lw04vnSeAiMRdcgbmw5RDRuKBHt2pPJ8APokTFj
JavaScript/TypeScript code that reproduces the crash?
No response
Relevant log output
No response
Stack Trace (bun.report)
Bun v1.1.10 (
5102a94
) on windows x86_64 [BuildCommand]panic: Expected pretty file path to have only forward slashes, got 'E:\deno\bun001\node_modules\figlet\lib\figlet.js'
debug.zig:373
:panicExtra
debug.zig:348
:panic
fs.zig:1724
:assertPrettyIsValid
bundle_v2.zig:2015
:runResolutionForParseTask
event_loop.zig:246
:run
time.zig:104
:nanoTimestamp
cli.zig:1450
:start
cli.zig:62
:start
main.zig:51
:main
exe_common.inl:78
:invoke_main
Features: tsconfig
The text was updated successfully, but these errors were encountered: