`deploy` should respect src/static about cargo-web HOT 3 OPEN

That's how it works; it just that the src/static directory currently only works for bin crates. (This is a historical artifact as originaly cargo-web supported only *-emscripten targets, and there you can only use bin crates.) Are you perhaps using a lib or a cdylib crate?

You can put a static directory in the root of your crate instead of in src and that will work for all crate types.

from cargo-web.

Ah, I am in fact using a lib crate, with the lib as the core to my binary. I wonder if there's any way to make that clearer? Or is there some reason that src/static and static/ aren't treated identically, other than that cargo-web used to behave differently? Maybe just combine the contents of all static/ directories into target/deploy/?, or error out if both static/ and src/static/ exist?

I'd be happy to try implementing one or both of these, just want to know which direction you'd like to go in.

from cargo-web.

Well, I think it would make sense to support src/static for lib crates too now that wasm32-unknown-unknown can be compiled as a cdylib crate.

Currently cargo-web takes static artifacts from two places (in this specific order):

• a target specific static directory (for bin crates this is src/static, for examples this is examples/$example_name-static)
• $crate_root/static - a global directory for all artifacts in your crate (so, binaries, libs, examples, etc.)

If it finds an artifact in the target specific path then it stops looking further. The idea was that if you have multiple things in your crate then you can put the common stuff in static, and thing-specific stuff in the respective target specific static directory, and have that "merged" together when running start or deploy.

from cargo-web.