Open Silvea12 opened 3 months ago
I encountered the same problem. I removed the ~/.cargo/assets path and it works.
... Why in the world does dioxus write to ~/.cargo? Seems to fix it but why would it write there? That in of itself feels like a bug.
Ah, I've found it. As per https://github.com/DioxusLabs/collect-assets/blob/c585779eaf615900f1a76f332905988da3922573/common/src/cache.rs#L11-L14 it uses home::cargo_home()
as a base - and this defaults to ~/.cargo
if unspecified.
I'm not sure I'd consider this good behavior - I feel like it should make something in the project root directory instead.
You might be running into https://github.com/DioxusLabs/collect-assets/issues/14. If you used a css file in the past with manganis and removed it, there is a bug that will cause it to not be removed.
We use a global directory instead of a directory in the project so that assets for a library are bundled into any crates that rely on that library
Problem
When creating a new dioxus fullstack project, the build will fail due to a missing input.css - something that is supplied with the tailwind css template. There is no reference to it in any files, and it's not a requirement of the web template.
Steps To Reproduce
Steps to reproduce the behavior:
dx new
fullstack
vanilla
true
dx build
ordx watch
Expected behavior
The build is successful - there is nothing depending on the input.css file at the project root.
Resulting behavior
Screenshots
N/A
Environment:
0.5.0
release, dioxus git9f280a8d84c183c74db3452d60a4601aa343813c
(main at time of project creation)1.77.1
Linux 6.8.2-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC x86_64 GNU/Linux
fullstack
Questionnaire