Closed LuckyTurtleDev closed 2 weeks ago
We currently hardcode the target directory in a few places in the CLI and hot reloading crates. We should read the cargo config instead
Talked about it - solution here is to properly use cargo's profiles mechanism to 1) allow parallel builds without our own custom target dir 2) not clobber rust flags 3) expose our own optimization flags
I split this issue out to #2780
We now use profiles in #2862 and no longer set a custom out dir.
Of course, if you're merging target dirs you're just gonna have a bad time due to a ton of reasons, but now at least we respect your target dir.
Problem If you use a custom target dir. The hot reload fails for dioxus full stack.
Steps To Reproduce
Steps to reproduce the behavior:
create
~/.cargo/config.toml
with the following contentsometimes you need to perform a change at the code to trigger this issue.
Expected behavior keep hot reload working?
Environment:
full-stack
]Questionnaire