Hi, I'm hitting some strange apparent caching with manganis. When I add it for an asset file it is served with random digits at the end – so works as expected. Then I remove all traces of manganis in my crate, run dx clean, cargo clean, and remove dist/. But on subseuqent dx serve it will again generate the file with random numbers in dist. It seems impossible to stop serving this file at all.
#manganis active after removal
1 messages · Page 1 of 1 (latest)
You can add const TAILWIND_CLASSES: &str = manganis::classes!("") with nothing else and it will remove the other asset
There is a bug with removing the last asset
Thanks! Out of curiousity, where is the dangling state causing this?
The first run of a manganis macro clears all assets for the current crate. If you don't have any macros, that logic doesn't run
https://github.com/DioxusLabs/collect-assets/pull/26 will fix this issue
I see, but where is that state hanging? I'd expect dx clean, cargo clean, and rm dist/ to remove anything the next run of manganis would see on the next compile
It is in your cargo home directory under the assets folder