Volodymyr Zhdanov

Uh that's an actual nightmare MS guys lost that ticket perhaps, it's been 2 years since the last update If nothing can be don't from plugin side, then there's no...

Well it happens only with this (or fsyh) plugin enabled Issue I linked higher has repro steps

I've checked https://github.com/preactjs/compat-alias-package, it seems to have proper exports. Can't really tell why this happens

> I see that the error is coming from `react-router-dom`. Have you tried using `deps.inline` with it? Currently files inside `node_modules` are not processed by Vite. They are executed by...

Other than react-router-dom I faced this error with styled components and recoil and probably other libraries that rely on `react`

Tried https://preactjs.com/guide/v10/getting-started#aliasing-in-rollup instead of alias package - this works in vite, but doesn't work in vitest even with https://github.com/vitest-dev/vitest/pull/1634

> One of the solutions from https://vitejs.dev/guide/ssr.html#ssr-externals: > > > If you have configured aliases that redirects one package to another, you may want to alias the actual node_modules packages...

> I wan't able to make your reproduction run Weird, `yarn install` + `npx vitest run` works fine for me on several devices > I would recommend opening an issue...

> If I add this to `/node_modules/react-router/package.json`, everything works fine tried doing this, getting this error: ``` FAIL src/app.test.tsx [ src/app.test.tsx ]Error: No "exports" main defined in C:\Users\wight\Documents\preact-vitest-repro\node_modules\react-router\package.json ❯ node_modules/react-router-dom/umd/react-router-dom.development.js:12:121...

Managed to fix most errors in main package codebase by patching package.json files in node_modules 8 files packages (would take months to get it fixed in those in best case),...