"TypeError: vi_esm_1.default.default is not a function" error when an expect assertion failed on browser mode

[Bnaya]

Describe the bug

There's a wacked "TypeError: vi_esm_1.default.default is not a function" error when an expect assertion failed on browser mode

Run this code in browser mode:

describe("vitest browser mode lets see", function () {
  test("lalla", async () => {
    expect(1).toBe(1);
    expect(1).toBe(2); // <- Failed assertion
  });
});

Reproduction

Not working on stackblitz!
https://stackblitz.com/edit/vitest-dev-vitest-cupgmf

System Info

System:
    OS: macOS 13.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 5.30 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.14.0 - ~/.volta/tools/image/node/18.14.0/bin/node
    Yarn: 3.2.0 - ~/.volta/tools/image/yarn/1.22.19/bin/yarn
    npm: 9.3.1 - ~/.volta/tools/image/node/18.14.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Chrome Canary: 116.0.5841.0
    Firefox: 112.0.2
    Safari: 16.5
  npmPackages:
    vitest: ^0.32.0 => 0.32.0

Used Package Manager

npm

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.
• 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.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• vitest-dev-vitest-cupgmf (Open reproduction)

[atmosbear]

Hi there, I'm still getting this issue: TypeError: __vi_esm_1__.default.default is not a function

Is it fully fixed? If it is I'll do some testing and start over from scratch to see if I need to make a new issue

[sheremet-va]

Fix is not released yet

[atmosbear]

Aww man. Is there a way to build it myself so that I can use it? It's really hard to do browser testing with it haha

[Bnaya]

Aww man. Is there a way to build it myself so that I can use it? It's really hard to do browser testing with it haha

If you are very inpatient, I would recommend using some form of package patching and not deal with publishing