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

@amalgm/shell

v0.1.109

Published

The Amalgm boot shell — the runtime assembled from published @amalgm SDK bricks. Composition and parity ground for the lego-driven engine rewrite.

Readme

@amalgm/shell

The Amalgm runtime, assembled from published @amalgm/* SDK bricks instead of the monolith. This repo is the composition and parity ground for the lego-driven rewrite of amalgm-engine — see PURPOSE.md for the axioms.

The first signed production release is intentionally Core + Files: Core owns machine login and readiness, Live owns the portable entity graph, and Shell injects the real filesystem, SQLite, watcher, and authenticated cloud wire.

Layout

  • src/boot.ts — assembles the HTTP/MCP runtime from bricks.
  • src/machine-host.ts — production effects injected into Core's machine setup.
  • src/user-ground-host.ts — production effects injected into Live registration.
  • src/wire-client.ts — the single authenticated gateway control path.
  • src/content-direct.ts — authorized direct-R2 download and local envelope opening.
  • src/watching/ — the single Node watcher host: physical coverage, routing, health, and retry; portable Watch law remains in @amalgm/live.
  • tests/ — parity, adapter, restart, watcher, and two-device examinations.

Run

npm install
npm test

# Isolated real-kernel Watch certification (macOS/Linux/Windows)
AMALGM_NATIVE_WATCH=1 node --test tests/watching/native.test.js

# PowerShell: $env:AMALGM_NATIVE_WATCH=1; node --test tests/watching/native.test.js

# First machine: browser approval or a setup code
npx --package @amalgm/shell amalgm login --no-open

# Resume one user on a machine that has several
npx --package @amalgm/shell amalgm run --user [email protected]

# In another shell, declare an external workspace; the running Watch performs registration
npx --package @amalgm/shell amalgm files register ./project --user [email protected]

# Materialize into the current directory and keep it on that same running Watch
npx --package @amalgm/shell amalgm files add <workspace-id> --user [email protected]

Requires Node ≥ 20.19 (native require(esm) support; all bricks are ESM).

Every push to main and every pull request runs the complete suite plus the isolated real-kernel Watch examination on GitHub-hosted Linux, macOS, and Windows machines. This certifies the same create, change, rename, move, delete, .git appearance/disappearance, and root-address mutations on every supported watcher backend. Production Fly/R2 examinations remain separate: CI proves the platform adapter, while the deployed examination proves the real cloud path.