v4: Vitest component tests crash on switch to svelte4

[cesarnml]

Describe the bug

Vitest test crash upon upgrading to svelte4.

Reproduction

Minimal Example Repo:
https://github.com/cesarnml/svelte4-testing-example

1. Git clone above repo.
2. pnpm i
3. pnpm test:unit

Logs

FAIL  src/routes/page.spec.ts [ src/routes/page.spec.ts ]
Error: No "exports" main defined in /Users/cesar/code/svelte4-testing-example/node_modules/.pnpm/@testing-library+svelte@3.2.2_svelte@4.0.0-next.0/node_modules/svelte/package.json
 ❯ Object.<anonymous> node_modules/.pnpm/@testing-library+svelte@3.2.2_svelte@4.0.0-next.0/node_modules/@testing-library/svelte/dist/pure.js:28:15

Serialized Error: {
  "code": "ERR_PACKAGE_PATH_NOT_EXPORTED",
}

### System Info

```shell
System:
    OS: macOS 13.4
    CPU: (8) arm64 Apple M1
    Memory: 84.80 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
    Watchman: 2023.05.22.00 - /opt/homebrew/bin/watchman
  Browsers:
    Brave Browser: 114.1.52.117
    Chrome: 113.0.5672.126
    Chrome Canary: 116.0.5813.0
    Firefox: 101.0
    Firefox Developer Edition: 114.0
    Firefox Nightly: 111.0a1
    Safari: 16.5
  npmPackages:
    svelte: 4.0.0-next.0 => 4.0.0-next.0

Severity

blocking all usage of svelte

[benmccann]

This looks to me like an issue with the way @testing-library/svelte is distributed. My recommendation would be that they remove the babel build step which should not be necessary and add "type": "module". Given that its for testing Svelte libraries, they should only need an ESM version and probably shouldn't be distributing it as CJS

Can you file the issue there?

[cesarnml]

@benmccann

Issue submitted.
testing-library/svelte-testing-library#220

[yanick]

Looking into it!

[benmccann]

I'm going to go ahead and close this since it looks like it'll be fixed by testing-library/svelte-testing-library#221 and there's not much to do in this repository. I'll be happy to reopen this if it turns out there is something we need to do here