Uncaught ReferenceError: document is not defined

[JS-mark]

Describe the bug

使用了 wasm

Reproduction

https://baidu.com

Steps to reproduce

pnpm dev

System Info

System:
    OS: macOS 14.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 1.20 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.1 - ~/.nvm/versions/node/v18.17.1/bin/node
    Yarn: 1.22.21 - /opt/homebrew/bin/yarn
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.1/bin/npm
    pnpm: 8.15.1 - /opt/homebrew/bin/pnpm
    bun: 1.0.18 - ~/.bun/bin/bun
  Browsers:
    Chrome: 123.0.6312.59
    Safari: 17.4
  npmPackages:
    @vitejs/plugin-basic-ssl: ^1.1.0 => 1.1.0
    @vitejs/plugin-vue: ^5.0.4 => 5.0.4
    vite: ^5.2.6 => 5.2.6

Used Package Manager

pnpm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[github-actions]

Hello @JS-mark. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[felladrin]

Also getting this error when running Vite in dev mode.
I am not sure yet what causes this, but it started happening on Vite v5.2.
A workaround is to downgrade it to v5.1. (npm install vite@~5.1)

[logicsb]

I have this error using ffmpeg.wasm. I've back to 5.1.7 and works fine. This error occur exactly when try to create an instance of the ffmpeg.

[JS-mark]

I have this error using ffmpeg.wasm. I've back to 5.1.7 and works fine. This error occur exactly when try to create an instance of the ffmpeg.

Yeah, I got back to normal when I was demoted to 5.1.7.

[felladrin]

Found the cause and created the minimal reproduction on StackBlitz:
https://stackblitz.com/edit/vitejs-vite-ghbtzp?file=vite.config.ts

Important:
Due to StackBlitz limitations, to see the results I mention below, you need to open the preview in a new tab:

Or download the files and run the demo locally.

---

When using Vite 5.2, the error starts happening when we add cross-origin isolation to the dev server:

    {
      name: 'configure-response-headers',
      configureServer: (server) => {
        server.middlewares.use((_, res, next) => {
          res.setHeader('Cross-Origin-Embedder-Policy', 'require-corp');
          res.setHeader('Cross-Origin-Opener-Policy', 'same-origin');
          next();
        });
      },
    },

---

Note how the app starts working again when the headers are removed:

    {
      name: 'configure-response-headers',
      configureServer: (server) => {
        server.middlewares.use((_, res, next) => {
-         res.setHeader('Cross-Origin-Embedder-Policy', 'require-corp');
-         res.setHeader('Cross-Origin-Opener-Policy', 'same-origin');
          next();
        });
      },
    },

---

cc @sapphi-red @ngxson

[jlarmstrongiv]

Related to #15852 (comment)