npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@stacks/clarinet-sdk-wasm

v3.12.0

Published

The core lib that powers @stacks/clarinet-sdk

Downloads

1,569

Readme

Clarity SDK WASM

This component exposes Clarinet features to a JS interface through wasm-bindgen. It's built with wasm-pack.
It powers @stacks/clarinet-sdk and @stacks/clarinet-sdk-browser.

Contributing

Build package

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 stacks --out-dir pkg-node --target nodejs

Build for the browser

wasm-pack build --release --scope stacks --out-dir pkg-browser --target web

Release

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