yosh

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.

assuming publishing to crates.io, then to npm: npm already has prepublish – running a bunch of cargo commands there should be same as running a bunch of npm commands in a cargo postpublish, right?

True! - but if it's an actively developed Rust project, it would probably feel odd to use npm commands to do all the Rust things haha. I'm thinking like a _full_ auto deploy for Rust - just multiple output targets, and perhaps an epiphemeral package.json file :D

i am working on tool to do exactly this hehe