-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 11: Weird path resolving issue #67
Comments
Most likely. This project has not been tested on Windows. |
I have the same issue on Windows 10. Please make it also available for Windows! Thnx, Digging through the load-config.js file this is the error message: Running WSL (Windows Subsystem for Linux) might solve issues with the paths, but I'm not allowed to use that. |
config file gets loaded properly in WSL. |
Got the same error in Windows 10. Tried custom config path via cli as well but same error. Cannot use custom ladle config on Windows. Perhaps path normalization is needed. |
Would be useful if ladle can extend the vite.config.js or have a way to inject custom vite config so we can put our own vite plugins if required. |
Decided to give ladle a try on a new project. It worked fine until I tried to add a .ladle/ dir for some config bits. Below is the result of running
yarn ladle serve
. Notice in particular that the config.mjs isn't detected, and the path.............ladleconfig.mjs
seems out of nowhere. Running on Windows 11, if that makes a difference.The text was updated successfully, but these errors were encountered: