fix: fix module resolution for esm file

[sheremet-va]

Fixes #1483

[netlify]

✅ Deploy Preview for vue-test-utils-docs ready!

Name	Link
🔨 Latest commit	fc8e462
🔍 Latest deploy log	https://app.netlify.com/sites/vue-test-utils-docs/deploys/6277629ec47dae0008db1728
😎 Deploy Preview	https://deploy-preview-1484--vue-test-utils-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[sheremet-va]

Also, this should help with calling createElement on undefined in Vitest, because now vite.config will call cjs Vue version, but @vue/test-utils will call new esm version, when jsdom will be defined.

[lmiller1990]

Nice, thanks.

Docs for this is anyone else (like me) was not familiar w/ the exports key: https://nodejs.org/api/packages.html#subpath-exports

[veitbjarsch]

@sheremet-va @lmiller1990

Also, this should help with calling createElement on undefined in Vitest, because now vite.config will call cjs Vue version, but @vue/test-utils will call new esm version, when jsdom will be defined.

How do I ensure that the esm package is called when I use jsdom? I have the problem that it will load the browser package, which search for Vue in globalThis. There is a dirty workaround with

testEnvironmentOptions: {
    customExportConditions: ['node', 'node-addons'],
  },

But this can't be the soltuion.

[lmiller1990]

Vite should be loading the ESM version - I don't think this is an issue in Test Utils. Can you make a minimal reproduction and share it (probably in the Vitest repo)?

[veitbjarsch]

It might not relate to Vitest but to jest, because there I receive this problem since the update. I can try to create a repo where I reproduce the issue.

[sheremet-va]

It might not relate to Vitest but to jest, because there I receive this problem since the update. I can try to create a repo where I reproduce the issue.

The error happens, because Jest prioritises "browser" condition, when jsdom is enabled

[veitbjarsch]

It might not relate to Vitest but to jest, because there I receive this problem since the update. I can try to create a repo where I reproduce the issue.

The error happens, because Jest prioritises "browser" condition, when jsdom is enabled

Yeah but this should be the case. Because if I use jsdom I wanna test the behavior like I'm in the browser. So in my opinion prioritizing the browser would be correct. But I'm not sure why we need a browser package for vue test utils which depends on a global registered vue version.

[sheremet-va]

Because if I use jsdom I wanna test the behavior like I'm in the browser

You should not expect browser packages behave the same in Node as they do in browser. These are two different environments, so I wouldn't say that jest does anyone good by including it by default, since it's running inside Node.

[lmiller1990]

This kind of thing is why I moved a lot of my tests to Cypress instead of Jest + jsdom...

If there's action to be taken here to improve the testing experience with Test Utils here, happy to do so, but we definitely need 1) minimal repro and 2) verify with the runner(s) or environments in question that there's actually a bug.