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-plakboek

v0.6.0

Published

Scaffold a Plakboek host project with npx create-plakboek

Readme

create-plakboek

Scaffold a Plakboek host project.

npx create-plakboek my-site

The command writes a project from the starter template that ships inside this package. Nothing is fetched from the network to build the project; only the dependency install that follows talks to the registry.

Requires Node.js 22.22 or later and pnpm.

What it asks

| Prompt | Flag | Default | | ---------------------------------------------------- | ------------------ | -------------------------------- | | Project directory | [dir] or --dir | my-plakboek-site | | Site name (1 to 200 characters) | --site-name | the directory name in Title Case | | Default locale | --locale | en | | Additional locales (comma-separated, blank for none) | --locales | nl with --yes; blank is none |

A flag skips its prompt. When standard input is not a terminal, every value must come from a flag or from --yes; a missing value fails with Error: {flag} is required when input is not interactive. instead of waiting for input.

Other options:

  • --yes (-y) accepts every default without asking.
  • --timezone <name> sets the site's IANA time zone (default: this machine's).
  • --skip-install skips pnpm install and the formatter run, and adds pnpm install to the printed next steps.
  • --help (-h) and --version (-v).

What it does

  1. Refuses a directory that already holds files. Files are created exclusively, so nothing is ever overwritten.
  2. Copies the starter, filling the site name, locales, time zone, package name and the version of the @plakboek/* packages (the generated project pins them to this CLI's own version).
  3. Runs git init, then pnpm install, then the project's formatter.

If the install fails, the project directory is kept and the command tells you to run pnpm install there. The command never deletes what it wrote.

Exit codes

| Code | Meaning | | ---- | ----------------------------------------------------------------- | | 0 | The project was created | | 1 | Unsupported Node.js, pnpm missing, or a failure while creating it | | 2 | Bad usage: an unknown flag, an invalid answer or a missing value |