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

@tomina/deploy-echoes

v1.0.0

Published

Keep old static-site paths resolving by carrying archived files forward on each deploy.

Readme

@tomina/deploy-echoes

Small CLI for static-site deployment on simple CDN-backed hosts such as GitHub Pages.

deploy-echoes is for sites where recently removed files still need to stay deployable for a while, but your host/CDN cannot simply delete content older than a chosen retention age. It rebuilds a publishable output from the current build plus archived previous deploys so old paths can keep resolving until they age out of the archive window.

Quick start

npm install --save-dev @tomina/deploy-echoes
npx deploy-echoes https://username.github.io/your-site/deploy-echoes/
  • The CLI argument is the public URL of the published archive directory, not the site root.
  • The archive directory must be published with the site output.
  • By default that directory is deploy-echoes, so a site rooted at https://username.github.io/your-site/ would publish archives at https://username.github.io/your-site/deploy-echoes/.
  • Run deploy-echoes --help for detailed flags.

What it is not for

  • Atomic deploys
  • Rollback management
  • Traffic shifting
  • Independently versioned sites under separate URLs

License

ISC - see LICENSE.