Run & review this pull request in StackBlitz Codeflow.

Hello, I am having issues with migrating our large frontend repo from CRA to Vite because of this specific error

It is really hard to understand how I can avoid this without changing the vite package manually in node_modules. Maybe there is some sort of setting that could help me avoid it, or avoid using some sort of dynamic import? But I am not familiar enough to understand why this is happening.

@patak-dev could you bump the severity of this bug?

@patak-dev hi! Could I ask you to prioritise this if possible? The issue currently blocks updating Gitlab to Vite 5.1.4 because it breaks build stage.

BTW @morethanwords thank you for this fix!

/ecosystem-ci run

📝 Ran ecosystem CI on eea6083: Open

✅ analogjs, astro, histoire, ladle, laravel, marko, nuxt, previewjs, qwik, rakkas, sveltekit, unocss, vike, vite-plugin-pwa, vite-plugin-react, vite-plugin-react-pages, vite-plugin-react-swc, vite-plugin-svelte, vite-plugin-vue, vite-setup-catalogue, vitepress, vitest

@SimonsUnikaNamn @CyberAP this should be fixed in [email protected]. Let us know if you still see a problem.