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

@zeropress/build

v0.5.2

Published

ZeroPress full-build CLI

Vulnerabilities

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

Links

Git

Maintainers

laelbelaelbe

Keywords

zeropressstatic-site-generator

Readme

@zeropress/build

npm license node

ZeroPress full-build CLI.

This package is the public CLI wrapper around @zeropress/build-core.

Install

# Run directly with npx
npx @zeropress/build --help

# Or install globally
npm install -g @zeropress/build
zeropress-build --help

Quick Start

npx @zeropress/build ./theme --data ./preview-data.json

Usage

zeropress-build <themeDir> --data <path> [--out <dir>]

Arguments

  • <themeDir>: Theme directory to render

Options

  • --data <path>: Canonical preview-data v0.5 JSON file
  • --out <dir>: Empty output directory, default ./dist
  • --help, -h: Show help
  • --version, -v: Show version

Examples

zeropress-build ./my-theme --data ./preview-data.json
zeropress-build ./my-theme --data ./preview-data.json --out ./dist/site

Inputs

Theme Directory

Preview Data

  • --data <path> must point to canonical preview-data v0.5 JSON
  • The payload is validated by @zeropress/build-core against the canonical preview-data v0.5 contract
  • Optional custom_html is treated as trusted site-level HTML and may inject markup before </head> and </body>
  • Only provide custom_html from trusted admin/generator input; ZeroPress does not sanitize that HTML

Public Directory

  • If the resolved public directory exists, its files are copied to the output root before generated ZeroPress files are written
  • The public directory name itself is not included in the output path
  • There is no --public-dir option; set ZEROPRESS_PUBLIC_DIR when a project needs a different public root
  • ZEROPRESS_PUBLIC_DIR defaults to ./public/; relative values are resolved from the current working directory
  • Public files can be used for files such as favicon.ico, ads.txt, third-party assets, source files, images, and PDFs
  • If a public file and a generated ZeroPress file use the same output path, the generated file wins
  • robots.txt is the exception: a root-level public robots.txt is treated as the site owner's robots policy and prevents ZeroPress fallback robots.txt generation
  • When public robots.txt exists, ZeroPress copies it as-is and does not append a Sitemap directive. Add Sitemap: https://example.com/sitemap.xml manually when needed.
  • Root-level public favicon files named favicon.ico, favicon.svg, favicon.png, and apple-touch-icon.png are auto-discovered and injected into generated HTML <head> output unless preview-data already defines site.favicon
  • Hidden entries, node_modules, Thumbs.db, *.key, *.pem, and symlinks inside the public directory are ignored
  • The theme directory and output directory must not overlap with the resolved public directory

Output

  • If --out is omitted, output is written to ./dist relative to the current working directory
  • The output directory must not already contain files before the command runs
  • The output directory must be empty before public files are copied
  • On success, the CLI prints generated file count, output directory, and elapsed time
  • Full-build output includes the normal artifact set such as index.html, post and page routes, hashed assets, sitemap.xml, feed.xml, and fallback robots.txt
  • If preview-data sets site.indexing: false, the generated fallback robots.txt disallows all agents. Custom crawler policies should be provided as public robots.txt.

Supported

  • Full build only
  • Local theme directory input
  • Local preview-data JSON input

Not Supported

  • Selective or patch build input
  • Config files
  • Remote preview-data URLs
  • Deployment or publish integration

Requirements

  • Node.js >= 18.18.0
  • ESM only

Related

License

MIT