I am here because what I just did feels wrong, and I'm tattling (on myself) to you for not knowing a better way. I added a package.json to my rust repo just to get a dev-tooling experience that is documented/easy:
Run npm start and then open your browser. It will pick up backend/html/CSS changes and recompile for you.
The crutch here feels like concurrently -- I want two processes watching their own files/directories for changes and running commands, so the user just has to refresh their browser and pick up new code. Is there an equivalent to concurrently in a rust package? Does anyone know of a good replacement that I can document as an easy way to get started on my repo?
in case I lost you, maybe this screenshot of the npm start results helps show what I'm trying to get (without a package.json):
Thanks will give it another shot, but I'll reiterate what cargo watch felt like it was missing -- you have one ignore shared by all your cargo commands right? My two commands care about separate files. I don't need to recompile rust if only styles change, and vice versa.
The rust ecosystem is currently pretty weak dealing with the sorts of things npm scripts are used for unfortunately.
Your current best bet for that sort of thing I think is to add a scripts internal crate to your workspace, then add an alias to .cargo/config.toml that calls cargo run -p scripts [...args]. Then make this scripts crate call back into cargo or whatever, with whatever behavior you want. It's a lot more work, but a lot more flexible.