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

@the-smithy/create-hearth-site

v0.19.0

Published

Start a new client website powered by Hearth: pnpm create @the-smithy/hearth-site

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

the-smithythe-smithy

Keywords

Readme

@the-smithy/create-hearth-site

Starts a new website powered by Hearth, The Smithy's headless CMS: a Next.js site with every content block rendered, SEO, forms, live preview and the publish webhook, ready to restyle.

It needs API access to Hearth. The site reads all of its content from a Hearth site with that site's API key, so it shows nothing without a Hearth account. Developer access is by invitation: request it at hearth.thesmithy.io/developers.

Before you start

  • Node 20.9 or later, and pnpm (run corepack enable once if pnpm isn't found).
  • The site's address in Hearth: open the site in Hearth and copy the part after /admin/sites/ in the address bar. For hearth.thesmithy.io/admin/sites/acme/pages it's acme.

Create the site

From the folder where you keep your projects, run:

pnpm create @the-smithy/hearth-site@latest acme-website --site acme

Replace acme-website with the folder to create and acme with your site's address. Each part:

| Part | What it is | | --- | --- | | pnpm create @the-smithy/hearth-site@latest | Runs this package. pnpm create @the-smithy/hearth-site is pnpm's short form of @the-smithy/create-hearth-site. Keep @latest: without it, pnpm skips releases less than a day old and quietly uses an older one | | acme-website | The folder to create, which also names the project. It must not exist yet, or must be empty | | --site acme | Your site's address in Hearth (lowercase letters, numbers and dashes). Written to .env.local as HEARTH_SITE |

Leave out the folder or --site and you're asked for them. Add --skip-install to skip pnpm install.

The command copies the starter into the new folder, writes .env.local with the site's address, runs git init and installs the packages. Then:

cd acme-website

Add an API key to .env.local (Hearth → the site → API & webhooks → API keys), and run pnpm dev. The new site's README walks through the first run, previews, deploying and troubleshooting.

Documentation

Once you have developer access, the full documentation is in your Hearth account under API docs.

License

For use with Hearth. See LICENSE.