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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@holochain/hc-spin-rust-utils

v0.700.0

Published

`@holochain/hc-spin-rust-utils` is a node add-on used by - [@holochain/hc-spin](https://github.com/holochain/hc-spin) - [kangaroo-electron](https://github.com/holochain/kangaroo-electron)

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

zippy314zippy314zo-elzo-eljost-sjost-smatthmematthmethetasinnerthetasinnerveesoveesocallum.dunstercallum.dunstermattygmattyg

Keywords

Readme

hc-spin-rust-utils

@holochain/hc-spin-rust-utils is a node add-on used by

At the time of writing it contains two main pieces:

  • A utility function unpackAndSaveWebhapp that takes a path to a .webhapp file, unpacks the .webhapp file into UI assets and .happ file and stores them at respective paths specified in the function arguments.
  • A ZomeCallSigner object that connects to a running instance of lair keystore and exposes a method signZomeCall to have lair sign zome calls for a specified public key.

Supporting a new Holochain version

Once a new version of Holochain is released, support for it can be added by following these steps:

  1. Update the crates in Cargo.toml as necessary and make any required changes in case of compilation errors. Do NOT change the package version in package.json. This will be done automatically when creating a new release.
  2. Test the package locally by
    1. Building it: npm run build
    2. Linking it globally with yarn: yarn link
    3. Inside a local hc-spin repository, use the linked local package: yarn link @holochain/hc-spin-rust-utils and test that hc-spin works and zome calls succeed (you may want to unlink it again after testing with yarn unlink @holochain/hc-spin-rust-utils).
  3. If testing succeeds, commit the changes and make a PR to main or main-xx where xx is the Holochain version branch, for example main-06 contains new Holochain v0.6.x versions. This will trigger a CI test run that builds the package for all platforms but does not publish it.

Release process

To release a new version of @holochain/hc-spin-rust-utils, you may proceed as follows:

  1. Trigger the Prepare Release action with the desired new version number on the corresponding branch (main for the Holochain main branch and main-xx for older versions).
  2. This will bump the versions, generate a changelog, and open a PR for these changes.
  3. Review and manually edit the PR on the working branch where required.
  4. Merge the PR with a rebase-merge. This will trigger the Publish Release workflow which will build the packages and publish them to NPM via Trusted Publishers and to GitHub as a release with artifacts.