You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our current build.rs is handling a lot of various functionality pertaining to the release, installers and npm. To automate and test these separate pieces, we should consider switching to using [cargo-xtask](https://github.com/matklad/cargo-xtask).
I see us have a few xtasks:
cargo xtask npm - to generate all applicable work for our npm package
cargo xtask release -- to handle release management and prep
cargo xtask dist seems to be the pattern for making release stuff happen, and cargo xtask ci could include running our clippy + tests stuff, everything currently in lint.yml could be slurped up here.
Description
Our current
build.rs
is handling a lot of various functionality pertaining to the release, installers and npm. To automate and test these separate pieces, we should consider switching to using[cargo-xtask](https://github.com/matklad/cargo-xtask)
.I see us have a few xtasks:
cargo xtask npm
- to generate all applicable work for our npm packagecargo xtask release
-- to handle release management and prepcargo xtask install
-- to handle installationsPrior Art
A few good examples for us to look at:
cargo xtask
itself has a good hello-world example.rust-analyzer
utilises it a bunch for codegen, release and installation management. Tools of interest:The text was updated successfully, but these errors were encountered: