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

@shadw/node

v0.1.0

Published

Boot a real shadw platform node locally, as easily as any other npx dev tool

Vulnerabilities

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

Links

Git

Maintainers

openclewopenclew

Keywords

Readme

@shadw/node

Boot a real shadw platform node locally — as easily as any other npx dev tool. This runs the actual hive-cloud server binary (the same one every fleet node runs), not a simulation of one.

npx @shadw/node

That's it (npm resolves a scoped package's sole bin entry regardless of name, so this runs the shadw-node command — the same mechanism @angular/cli/@vue/cli use). It boots a single local node with sane dev defaults:

HIVE_FORCE_MOCK=1 HIVE_DATA=~/.shadw-node hive-cloud \
  --name local --listen 127.0.0.1:8787 --admin 127.0.0.1:8786

Then:

curl http://127.0.0.1:8786/healthz
npx @shadw/cli --api http://127.0.0.1:8786 auth login   # point the CLI at it

Pass any argument yourself and you get full control, zero injected defaults — shadw-node becomes a thin exec wrapper around hive-cloud at that point:

npx @shadw/node --name mynode --listen 0.0.0.0:8787 --admin 127.0.0.1:8786

Why HIVE_FORCE_MOCK=1 by default

This tool is for local dev and demos, not production fleet nodes. Production nodes are provisioned through this repo's own ansible roles, which do real hardware/KVM detection, mesh bootstrap, TLS certificates, and more. shadw-node mirrors scripts/dev-cluster.sh's single-node shape instead: functions run as real host processes (the same isolation tier the platform's own mock-backend fleet nodes use), with no assumption that your machine has KVM or Firecracker available. Set HIVE_FORCE_MOCK=0 yourself if you know what you're doing and want the real backend-selection logic to run.

Platforms

| Platform | Package | Status | |---|---|---| | macOS (Apple Silicon) | @shadw/node-darwin-arm64 | ✅ built + locally verified (real node booted, healthz answered) | | macOS (Intel) | @shadw/node-darwin-x64 | ✅ built | | Linux (x64) | @shadw/node-linux-x64 | 🚧 built by CI (.github/workflows/release-npm-cli.yml) on the next cli-v* tag | | Linux (arm64) | @shadw/node-linux-arm64 | 🚧 built by CI on the next cli-v* tag |

This is a real platform server binary (~75-80 MiB, stripped) — large compared to a typical npx tool, and that's inherent to shipping a real distributed systems node rather than a bug to fix.

Source

Wraps hive-cloud in this monorepo. scripts/build-npm-pkg.sh is the single source of truth for how every platform package here is built and staged.