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

@budhash/zap-sh

v1.1.2

Published

JavaScript generator for zap-sh scripts — byte-for-byte parity with the bash `zap-sh init` oracle.

Readme

@budhash/zap-sh

A JavaScript generator for zap-sh scripts. It produces the same output as the bash zap-sh init command, byte-for-byte: a shared conformance suite runs the same fixtures through both the bash and JS generators in CI, so their output stays in sync. See the generation spec.

It covers init (generation) only — template choice, project metadata, license, and variable substitution. Use the bash tool for update, snip, and upgrade.

Install

npm install @budhash/zap-sh

Usage

import { generate } from '@budhash/zap-sh';

const { filename, content } = generate({
  template: 'enhanced',          // 'basic' | 'enhanced'
  project: 'my-tool',            // becomes {{app}}; /^[a-zA-Z0-9_-]+$/
  license: 'mit',                // 'mit' | 'apache' | 'gpl' (optional)
  year: '2025',                  // pins {{year}} (optional; defaults to current year)
  variables: {                   // extra {{key}} values; order is significant
    author: 'Jane Doe',
    email: '[email protected]',
    version: '1.2.0',
    detail: 'Short description',
    description: 'Longer description',
  },
});

// content === what `zap-sh init my-tool -t enhanced --license=mit ...` writes
// filename === 'my-tool.sh'

CommonJS works too:

const { generate } = require('@budhash/zap-sh');

API

  • generate(options) => { filename, content } — generate a script. Throws on an invalid template, project name, variable name, or license code.
  • substitute(content, pairs) — the {{key}} substitution engine (sequential, whole-buffer; see SPEC §4).
  • extractSection(templateText, name) — extract a ##( name … ##) name section (markers included), or null.
  • listTemplates() / listLicenses() — available names / license codes.

Full types in types/index.d.ts.

Determinism

year is the only clock-derived input. Pass year to make output fully reproducible; omit it to use the current year. See SPEC §6 for the one edge ({{year}} embedded inside a field value) that remains clock-bound.

Development

The templates are bundled from the repo's templates/ at build time (the single source of truth), so src/templates.generated.js and dist/ are generated.

npm run build     # bundle templates + emit dist/index.mjs + dist/index.cjs (pure Node, no deps)
npm test          # build, then conformance vs the shared golden files
npm run test:diff # differential parity: run the live bash tool + JS and diff

The package has zero dependencies — the build is plain Node (no bundler).

Parity is enforced in CI two ways: the JS and bash conformance runners both check the same fixtures in test/conformance/, and the differential test runs the live zap-sh init and the JS generator over a broad input matrix and compares byte-for-byte.