@hirosystems/clarinet-sdk-wasm
Advanced tools
This component exposes Clarinet features to a JS interface through wasm-bindgen.
It's built with wasm-pack.
It powers @hirosystems/clarinet-sdk and
@hirosystems/clarinet-sdk-browser.
Install wasm-pack.
In the root directory of Clarinet, run the following command to build the packages for Node.js and the browser.
Under the hood, it will run wasm-pack build twice, once for each target.
npm run build:sdk-wasm
Alternatively, it's also possible to build the packages separately. It should only be done for development purpose.
Build for node
wasm-pack build --release --scope hirosystems --out-dir pkg-node --target nodejs
Build for the browser
wasm-pack build --release --scope hirosystems --out-dir pkg-browser --target web
The package is built twice with wasm-pack as it can't target node and web at the same time.
The following script will build for both target, it will also rename the package name for the
browser build.
npm run build:sdk-wasm
Once built, the packages can be released by running the following command. Note that by default we release with the beta tag.
npm run publish:sdk-wasm
3.0.0 (2025-05-07)
While most recent features were shipped in the 2.x series, this 3.0.0 version allows us to stabilize the Clarity Formatter and Mainnet execution simulation features.
With a major version bump comes breaking changes, especially since the Clarinet JS SDK will now use Stacks.js v7. The most significant change for Clarity developers is how Stacks.js handles Clarity values. See the Stacks.js migration guide for more details.
FAQs
The core lib that powers @hirosystems/clarinet-sdk
The npm package @hirosystems/clarinet-sdk-wasm receives a total of 973 weekly downloads. As such, @hirosystems/clarinet-sdk-wasm popularity was classified as not popular.
We found that @hirosystems/clarinet-sdk-wasm demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers
Security News
pnpm's new minimumReleaseAge setting delays package updates to prevent supply chain attacks, with other tools like Taze and NCU following suit.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.