I've run into a very weird issue with vite-tsconfig-paths, my project suddenly stopped working without me changing anything in it.
After a few hours of debugging, I managed to narrow down the issue and reproduce it in a new Vite+React+TS project. The issue is caused by vite-plugin-svgr, but only on Windows 10 with the latest updates (I suspect it's KB5039211).
Not sure if this is really an issue with vite-plugin-svgr, my actual project doesn't work even when the plugin is removed. 🤔 Unfortunately, I can't narrow down when it stops working.
I've run into a very weird issue with vite-tsconfig-paths, my project suddenly stopped working without me changing anything in it.
After a few hours of debugging, I managed to narrow down the issue and reproduce it in a new Vite+React+TS project. The issue is caused by
vite-plugin-svgr
, but only on Windows 10 with the latest updates (I suspect it's KB5039211).The project works perfectly fine on StackBlitz - https://stackblitz.com/edit/vitejs-vite-vmbggc?file=src%2FTest%2FTest.tsx,src%2FApp.tsx,tsconfig.app.json,vite.config.ts&terminal=dev, it works on my outdated Win11 VM, but not on the latest Win10. The issue happens regardless of NodeJS version.
When
svgr(...)
is commented out in plugins, it starts working again.I don't know where to even start debugging this. Here's the output of
SET DEBUG=vite-tsconfig-paths && npm run dev
: