fix: set customExportConditions to ['']

[kettanaito]

Move the customExportConditions from userland to this package to ensure msw/node is resolved correctly in Jest.

[kettanaito]

Released: v0.0.9 🎉

This has been released in v0.0.9!

• 📄 Release notes
• 📦 npm package

Make sure to always update to the latest version (npm i jest-fixed-jsdom@latest) to get the newest features and bug fixes.

---

Predictable release automation by @ossjs/release.

[jiri-prokop-pb]

Hey, just FYI. This change is breaking our usage, unfortunately.

We'd prefer to keep it the previous way.

The problem is that with more complicated setups, you can't enforce export conditions to be [''] because it can break other things one uses in Jest.

For reference, right now we have the following patch for jest-runtime:

diff --git a/build/index.d.ts b/build/index.d.ts
index 5bdf9fdf30fd0f28a1760ac41404238b61b20b94..4936148bb1fc4ad390f183ebd2d5a0db75179873 100644
--- a/build/index.d.ts
+++ b/build/index.d.ts
@@ -84,6 +84,8 @@ declare class Runtime {
   private jestGlobals?;
   private readonly esmConditions;
   private readonly cjsConditions;
+  private readonly esmConditions_msw;
+  private readonly cjsConditions_msw;
   private isTornDown;
   constructor(
     config: Config.ProjectConfig,
diff --git a/build/index.js b/build/index.js
index 01cb4206525dab0e564e07366bb0de1cc68ae2d1..9d6c0a0da432c4e71bf7cb4b778d7349247062a0 100644
--- a/build/index.js
+++ b/build/index.js
@@ -266,6 +266,8 @@ class Runtime {
   jestGlobals;
   esmConditions;
   cjsConditions;
+  esmConditions_msw;
+  cjsConditions_msw;
   isTornDown = false;
   constructor(
     config,
@@ -335,6 +337,8 @@ class Runtime {
     this.cjsConditions = Array.from(
       new Set(['require', 'default', ...envExportConditions])
     );
+    this.esmConditions_msw = [...new Set(['import', 'default', ''])];
+    this.cjsConditions_msw = [...new Set(['require', 'default', ''])];
     if (config.automock) {
       config.setupFiles.forEach(filePath => {
         if (filePath.includes(NODE_MODULES)) {
@@ -1274,14 +1278,22 @@ class Runtime {
   _resolveCjsModule(from, to) {
     return to
       ? this._resolver.resolveModule(from, to, {
-          conditions: this.cjsConditions
+          conditions:
+            ['msw', 'msw/node'].includes(to) ||
+            to.startsWith('@mswjs/interceptors')
+              ? this.cjsConditions_msw
+              : this.cjsConditions
         })
       : from;
   }
   _resolveModule(from, to) {
     return to
       ? this._resolver.resolveModuleAsync(from, to, {
-          conditions: this.esmConditions
+          conditions:
+            ['msw', 'msw/node'].includes(to) ||
+            to.startsWith('@mswjs/interceptors')
+              ? this.esmConditions_msw
+              : this.esmConditions
         })
       : from;
   }

Without this many of our tests were failing with the solution suggested in MSW's doc.

Some time ago I started creating PR for Jest to allow specify export conditions in a more granular way but I wasn't able to finish it yet as I have other more important tasks. The patch above was just a hacky way to do it but I struggled to create something nice and generic.

So, maybe consider this 🙏

(Note: we are in transition to vitest right now but it may take us couple of weeks to finalize it in our monorepo)

[kettanaito]

@jiri-prokop-pb, if this is breaking for you, provide a customExportConditions property override in your Jest config and list any other conditions you need after 'node'.