'Error: No known conditions for "./node" specifier in "msw" package' when using MSW with Vitest #125

Activity

1. sanghunjlee commented on Mar 4, 2024

   

   sanghunjlee

   on Mar 4, 2024

   More actions

   Had the same issue earlier today.

   For those visiting this issue searching for solution, I went around this issue by adding an alias to resolve in the config file:

   // vite.config.ts
   
   export default defineConfig({
     // ...otherConfigs,
     resolve: {
       alias: [
         { find: "msw/node", replacement: "/node_modules/msw/lib/native/index.mjs"}
       ],
     }
   })

   Hope that helps.

   👍React with 👍2Reacted by stuartglass-dlg and EresDev
2. nknapp commented on Mar 19, 2024

   

   nknapp

   on Mar 19, 2024

   More actions

   I created an mswjs/msw#2092 at msw, but they said it's a problem of the framework (i.e. solid).

   I still have to try the workaround they proposed, but the reason for the error is that vite-plugin-solid sets "browser" as resolve.conditions here.

   This means that vite tries to load the browser-version of msw/node which does not exist.

   According to @kettanaito it is wrong to use browser for node.js, I personally think it is debatable.

   What I also noticed is that solid returns and empty render function when the resolve.conditions is set to "node". I don't really undestand why, but it seems wrong to assume that Node.js is only ever used for SSR.
3. nknapp commented on Mar 23, 2024

   

   nknapp

   on Mar 23, 2024

   Last edited by nknapp

   More actions

   So, after some more insights, my last statement is wrong. My current stance is that the package.json of mock-service-worker is not entirely correct. The resolve.conditions applied in this module actuall contains node. So it should be possible to load msw/node
4. brenelz commented on Sep 11, 2026

   

   brenelz

   on Sep 11, 2026

   Contributor

   More actions

   Can you retest with updated MSW/Vite/Vitest?
5. kettanaito commented on Sep 14, 2026

   

   kettanaito

   on Sep 14, 2026

   More actions

   There's been a ton of changes and improvements to both Vitest and MSW since this was open. I highly recommend trying to reproduce this on the latest versions of both libs. There's a very small chance it will still happen. We are testing all MSW packages in Vitest. I also know for a fast Vitest doesn't use the browser export condition unless you force it.
6. ryansolid

   added

   1.x

   on Oct 21, 2026