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

@gigaloom/web

v0.9.1

Published

Verified static Web operator assets for GigaLoom

Readme

@gigaloom/web

@gigaloom/web contains the verified, production-built browser assets for the GigaLoom operator interface. It is a static asset package, not a React component library, and it does not include the Python server or runtime.

Install and serve

Install the exact release alongside the service that will host the assets:

npm install --save-exact @gigaloom/[email protected]

Mount the package's dist/ directory at /web/assets/, preserving filenames, and serve dist/index.html for the operator route. The bundle uses hashed asset names and an absolute /web/assets/ base. Do not rewrite individual asset filenames.

The package includes:

  • dist/index.html and the production assets;
  • dist/manifest.json, the integrity and media-type manifest;
  • dist/_build/content-manifest.json, shared with the Python embedding;
  • dist/_build/provenance.json;
  • dist/_build/sbom.cdx.json;
  • dist/_build/licenses.json.

The manifest and evidence files describe this exact bundle. Consumers should reject missing files or digest mismatches instead of rebuilding or silently substituting assets.

Build and verify

From the repository root:

npm --prefix web ci --ignore-scripts
npm --prefix web run check
npm --prefix web run build:npm
npm --prefix web run pack:verify

build:npm performs one verified production build, writes the canonical ignored Python asset tree, and copies those exact bytes into the ignored web/dist/ staging tree. pack:verify runs npm pack --dry-run --json, compares the complete package inventory with the declared allowlist, and rejects source maps or embedded local absolute paths. Neither command publishes the package.

The Python wheel uses a separately staged copy of the same Web build. Release automation is responsible for proving byte-for-byte parity before either artifact is eligible for publication. Node.js and npm are build inputs only; installed GigaLoom wheels do not require them.

The GigaLoom vector master lives in branding/gigaloom-mark.svg. npm run generate:brand refreshes the ignored generated Web copies.