Web workers do not work when runtime is edge

Link to the code that reproduces this issue

https://github.com/jauniusmentimeter/reproduction-app

To Reproduce

1. Start the application with next dev command
2. Open the page http://localhost:3000
3. The error "document is not defined is returned from the server"
4. Open app/page.tsx and change runtime to nodejs instead of edge. The error is not returned anymore.

Current vs. Expected behavior

Web workers do not work when runtime is set to edge. They should work in the same way as on nodejs runtime, since they are running on the client.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.0
  npm: 9.5.1
  Yarn: 1.22.21
  pnpm: 9.5.0
Relevant Packages:
  next: 15.0.0-canary.72 // Latest available version is detected (15.0.0-canary.72).
  eslint-config-next: N/A
  react: 19.0.0-rc.0
  react-dom: 19.0.0-rc.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Runtime, Webpack

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

Additional context

For some reason document is trying to be accessed on server environment when web worker code exist:

here is the place in .next/server/edge-runtime-webpack.js that is failing:

Start with the linked reproduction app, run it with next dev, and compare app/page.tsx using the edge and nodejs runtimes. Inspect the generated .next/server/edge-runtime-webpack.js location shown in the report; done means the web worker runs under the edge runtime without the server-side document is not defined error.