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

@saber-usa/node-common

v1.7.22

Published

Common node functions for Saber

Downloads

641

Readme

Node Common

Common nodejs functions used across a number of saber's applications.

Bulk WASM propagation

node-common is the single conduit for all satellite.js propagation in the Saber stack. As of v7, every primitive (prop, propGeodetic, the manual LookAngles chain) and every high-value high-level helper (getLeoRpoData, getGeoRpoData, getLeoWaterfallData, getGeoShadowZones) ships an async, WASM-backed *Bulk sibling (propBulk, propGeodeticBulk, propLookAnglesBulk, getLeoRpoDataBulk, getGeoRpoDataBulk, getLeoWaterfallDataBulk, getGeoShadowZonesBulk) that batches the work through satellite.js's BulkPropagator. The original sync functions are unchanged and still supported.

See docs/BULK_PROPAGATION.md for the full design rationale, lifecycle (lazy getBulkRuntime / eager initBulkRuntime / shutdown disposeBulkRuntime), per-thread pipeline registry, the measured break-even table (benchmarks/benchmarkBulkPropagator.js, npm run bench:wasmProp), the documented [email protected] lat/lon swap that propGeodeticBulk un-swaps internally, and the meanElements semantic gap on the WASM path.

License

AGPLv3

Publishing changes

  1. Increment the version in package.json
  2. Check you are logged in to npm using npm whoami
  3. You may need to login using npm login note your npm user must have 2FA enabled (in your profile)
  4. Run npm install npm login then npm publish

Run SonarQube Scan

To run SonarQube locally:

docker run -d --name sonarqube -p 9000:9000 sonarqube:latest

Go to http://localhost:9000 (default credentials: admin / admin).

Create a local project (NPM) and generate a token.

Run a scan on this project:

sonar -Dsonar.host.url=http://localhost:9000 -Dsonar.token=<your_sonarqube_token> -Dsonar.projectKey=node-common

MCP setup options:

  • Cursor: set token/url in .cursor/sonarqube.env (used by .cursor/mcp.json).
  • Claude Code: set token/url in .mcp.json (or copy from .mcp.json.example).

Note: for Dockerized MCP, use http://host.docker.internal:9000 as SONARQUBE_URL.