Loading duckdb wasm binary causes Turbopack to hang forever

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/compassionate-cray-jklgc5?workspaceId=ws_WCzEq2KEAJjTU1wDZNuBDJ ### To Reproduce 1. Run `next dev --turbopack` 2. Load localhost:3000 3. Observe that “Compiling / ...” is logged 4. Observe that “compiled in XXms” is never logged 5. Observe that the page never loads ### Current vs. Expected behavior “Compiling /” hangs forever; the page never compiles. ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4242 Available CPU cores: 2 Binaries: Node: 20.9.0 npm: 9.8.1 Yarn: 1.22.19 pnpm: 8.10.2 Relevant Packages: next: 15.4.0-canary.10 // Latest available version is detected (15.4.0-canary.10). eslint-config-next: N/A react: 19.1.0 react-dom: 19.1.0 typescript: 5.3.3 Next.js Config: output: N/A ``` ### Which area(s) are affected? (Select all that apply) Turbopack ### Which stage(s) are affected? (Select all that apply) next dev (local), next build (local) ### Additional context Occurs both during `next dev --turbopack` and `next build --turbopack` Very high CPU usage during while the page is not compiling The linked reproduction consists solely of - `import duckdbWasm from "@duckdb/duckdb-wasm/dist/duckdb-mvp.wasm";` - a line to prevent the import from being dead-code eliminated / tree-shaken: `console.log(duckdbWasm);`