Closed dugip closed 1 year ago
Same issues here with Vite, any known work around for this? Really like to get going with this lib but this is blocking me.
Thanks for reporting this. I have been looking into what is causing it, and it seems to be a change in the internals of vite. I haven't been able to come up with a fix yet, but using a lower version of vite should fix it in the meanwhile
I see, which version exactly? I'll downgrade for now.
Tried 3.2.7 and 2.7.0 but still get the same errors.
Hm yeah it looks like vite build --watch
doesn't work, but vite's HMR does if you are using a framework that makes use of that. Looks like an issue with how macaron resolves files – will try to find a fix for this
Any news here @Mokshit06? Is there I can help?
Unfortunately I didn't get the time to work on it. Will try to see if I can fix it this week. If you want to try working on it, I would start by adding breakpoints/logs to the resolveId
and load
callbacks, and seeing when they don't resolve with watch mode. This probably has something to do with the resolverCache
/cssMap
/idToPluginData
.
This should be fixed in the latest version. The issue was that macaron was clearing the cache before every build, so every time you changed something, it would clear the cache in watch mode and then vite couldn't resolve the file.
When using
vite build --watch
, the initial build works, but if you change the files to re-trigger a build, Macaron style generation will fail with the following error:Repro repo:
Steps to test:
yarn build