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

@jtfmumm/automerge-deps

v0.1.6

Published

CLI tool to fetch automerge module dependencies at build time

Readme

automerge-deps

CLI tool that fetches automerge-based module dependencies from a sync server and writes them to node_modules/ for use in a normal build.

Install

pnpm add -D @jtfmumm/automerge-deps

Setup

  1. Add an automerge-deps.json to your project root:
{
  "syncServers": [
    "wss://your-sync-server.example.com",
    "wss://fallback.example.com"
  ],
  "dependencies": [
    {
      "name": "@patchwork/contact",
      "url": "automerge:abc123"
    }
  ]
}

Usage

npx automerge-deps install

This connects to the first available sync server, fetches each dependency's folder document, and writes its files to node_modules/<name>/. Run it before pnpm build.

Sync servers are tried in order; if the first is unreachable, it falls back to the next.

Troubleshooting

If you see an error like Error: Document automerge:<url> is unavailable, try running the command again. The sync server may not have had time to deliver all sub-documents on the first attempt.

Preparing a dependency for publishing

Before pushing a dependency to a sync server, make sure it's ready to be consumed as a Node module. The fetched files are written directly to node_modules/<name>/, so the dependency must include:

  • A package.json with a main (or exports) field pointing to the compiled entry point
  • Compiled JavaScript output (e.g. run tsc before pushing if the source is TypeScript)

If a dependency was pushed without compiled output, you can work around it locally after fetching:

cd node_modules/<name>
npx tsc

You may also need to add a package.json with a main field pointing to the compiled entry point (e.g. dist/index.js).

Build from source

pnpm install
pnpm build
node dist/cli.js install