bug: Internal Server Error when running nextjs app locally on Windows

[nickreynolds]

Provide environment information

System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 35.56 GB / 63.91 GB
  Binaries:
    Node: 22.12.0 - C:\nvm4w\nodejs\node.EXE
    npm: 10.9.0 - C:\nvm4w\nodejs\npm.CMD
    pnpm: 9.15.2 - C:\nvm4w\nodejs\pnpm.CMD
    bun: 1.1.40 - ~\.bun\bin\bun.EXE

Describe the bug

From a fresh clone of this repo (on a windows machine), I ran pnpm i, set my DB URL, and then ran pnpm dev.

When I load localhost:3000 in the browser, I see "Internal Server Error" rendered, and the nextjs app logs look like this:

│>>> tRPC Request from rsc by undefined
│⨯ Internal error: TypeError: Cannot read properties of undefined (reading 'default')
at resolveClientReference (../../node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.edge.development.js:87:55)
│    at resolveModule (../../node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.edge.development.js:1667:35)       
│    at processFullRow (../../node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.edge.development.js:1740:25)      
│    at processBinaryChunk (../../node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.edge.development.js:1858:21)  
│    at progress (../../node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-client.edge.development.js:1926:17)
│    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
│digest: "4207119005"
│[TypeError: Cannot read properties of undefined (reading 'default')]
│ ⨯ [TypeError: Cannot read properties of undefined (reading 'default')]
│ ⨯ [TypeError: Cannot read properties of null (reading 'default')]
│ GET / 500 in 1804ms

Doing the exact same thing on my Mac does not show an error and the page renders correctly.

Link to reproduction

fresh clone of this repo

To reproduce

From a fresh clone of this repo, I ran pnpm i, set my DB URL, ran pnpm db:push, and then ran pnpm dev.

This is on windows, using Powershell (in VS Code) with nvm-windows installed.

Additional information

This appears to be a windows-only issue, but not sure why other users on Windows haven't reported it. For me, the project is entirely unusable for development on Windows.

[nickreynolds]

just to be sure, I uninstalled nvm-windows and manually installed nodejs@22, and the issue still persists

[nickreynolds]

I believe this issue is just related to this:

vercel/next.js#53562

I "fixed" my issue by removing the lines export const runtime = "edge";

Still, I think a note/warning should be added to the README so that developers know there is currently an issue with edge+nextjs+turbopack and they should remove those lines if using Windows for development.

[noxify]

hey @nickreynolds ,

there is already a note in the readme :)

[nickreynolds]

@noxify I guess my point is that the note should mention that Windows does not support the edge runtime with nextjs+turbo. The error message produced is not too helpful and it wasn't clear that disabling edge was what I needed to do to proceed.

[noxify]

Got it - maybe you could provide a PR with the changes to make it clear.

But I think it's a general problem, not only windows. ( please correct me if I'm wrong )

[nickreynolds]

@noxify I'll try to make a PR updating the note when I think of the right wording ;)

I'm not aware of any other dev envs that don't support edge runtime with turbo. The issue I linked describes a Windows-only issue. I suppose there probably are others, but I would let future contributors point those out when issues are encountered.