You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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.
Ohh, also just found about about "[package.metadata]" in Cargo.toml. Could easily do "[package.metadata.npm]" for npm specific things - and otherwise assume Rust libs should be published as "libname-wasm" on npm. Should make it reallll easy to publish hey.
The "main" target for the package.json could just directly be the WASM binary. Can easily inline it for the browser - but also serve up for streaming. Assuming `.wasm` can't be required yet in Node, doing `var libname = new Buffer(require.resolve('libname-wasm'))` should cut it.
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
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
