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

create-hedgerow

v0.1.1

Published

Create a local-first Astro publication backed by AT Protocol.

Readme

create-hedgerow

Create a complete Astro publication whose public source of truth is the author's AT Protocol repository.

Requires Node 22.12 or newer.

npm create hedgerow@latest my-site

The setup asks for an immutable author DID, canonical URL, and publication name. It generates source you own:

  • server-rendered article routes that read site.standard.* records;
  • public Bluesky comments, like counts, and reply links on discussed articles;
  • a local-first /sudo editor with TipTap, IndexedDB recovery, preview, diff, discard, Markdown import/export, and explicit publish;
  • browser OAuth metadata and callback routes with author-only permissions;
  • a one-time publication bootstrap script;
  • Standard.site publication/document verification links.

Run non-interactively in CI or tests:

npx create-hedgerow my-site \
  --author did:plc:example \
  --url https://example.com \
  --name "Example" \
  --no-install

--dry-run writes nothing. A non-empty target is rejected unless --force is supplied; force overwrites only matching generated files and never deletes unrelated files.

The generated editor is application source, not an opaque runtime package. Its marker records the generator version, but there is deliberately no promise of automatic merges after you customise it. Protocol/auth fixes remain upgradeable through hedgerow; product and visual decisions remain yours.

Drafts are unencrypted and device-local. The generated app requests persistent browser storage, detects cross-tab draft races, and includes Markdown export, but browser storage is not a backup. Published pages render article content on the server from a short PDS cache; the client only hydrates the social thread and authoring routes.

Pre-1.0, ESM-only. MIT.