You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And as such imports of these libraries are not correctly matched and processed during the build process.
Is the expectation that the transform libraries may be a combination of direct paths that need to adjust per OS and npm imports which will not change separators? Or could this separator safely always be "/"?
Steps to reproduce
Take any working vite/pigment configuration and attempt to run
vite:serve
on windows. It will not work (application does not load)Current behavior
Vite/Pigment build & serve broken on Windows
Expected behavior
Vite/Pigment build & serve should function on Windows in the same way as Mac, Linux
Context
We have a vite configuration for pigment which runs perfectly on Mac (and presumably Linux) but is entirely broken when run on Windows.
I have traced the issue to this line, which is using an OS-based
path.sep
.This is causing the transform libraries to be parsed like this.
And as such imports of these libraries are not correctly matched and processed during the build process.
Is the expectation that the transform libraries may be a combination of direct paths that need to adjust per OS and npm imports which will not change separators? Or could this separator safely always be "/"?
Your environment
npx @mui/envinfo
Search keywords: windows, vite
The text was updated successfully, but these errors were encountered: