I think all we need to bridge the boundary for publishing to crates.io & npm is a "post-publish" hook for cargo. Perhaps more hooks too would be grand (test, docs, bench), but this would be the baseline I reckon.
Show this thread
-
That makes sense! a `cargo npm` that builds a package.json from stuff you have in your cargo.toml doesn't sound far fetched, afaik https://crates.io/crates/cargo-deb … works like that (cargo subcommands are just binaries in
$PATH that are named cargo-NAME)
Ohhh, yeah that'd be really cool! - should make prototyping a workflow super easy. Also with: https://twitter.com/yoshuawuyts/status/955118247921246209 … it should be customizable enough! :D