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

npm-package-maker-lite

v0.1.1

Published

Scaffold and optionally publish npm packages from a local or remote JSON config.

Downloads

17

Readme

npm-package-maker-lite

Scaffold and optionally publish npm packages from a local file, a remote URL, or stdin JSON.

Install (local dev)

# in this folder
npm install

CLI usage

npmmaker --help

# From URL
npmmaker --from https://example.com/my-package-config.json --dir ./out/my-pkg
# With auth header
npmmaker --from https://api.example.com/configs/123 -H "Authorization: Bearer <token>" --dir ./out/my-pkg

# From local file
npmmaker --from ./config.json --dir ./out/my-pkg

# From stdin
cat config.json | npmmaker --dir ./out/my-pkg

# Start HTTP API server
npmmaker --serve --port 8787 --base-dir ./out --token mysecret

# Clean a generated directory
npmmaker --clean ./out/my-pkg

Example output:

Config format:

{
  "name": "my-lib",
  "version": "0.1.0",
  "description": "My generated lib",
  "main": "index.js",
  "type": "commonjs",
  "bin": { "my-lib": "./cli.js" },
  "scripts": { "test": "node -e \"console.log('ok')\"" },
  "keywords": ["demo"],
  "author": "",
  "license": "MIT",
  "files": ["index.js", "cli.js", "README.md"],
  "publishConfig": { "access": "public" },
  "filesMap": {
    "index.js": "module.exports = () => 'hello';\n",
    "cli.js": "#!/usr/bin/env node\nconsole.log(require('./index.js')());\n",
    "README.md": { "url": "https://raw.githubusercontent.com/user/repo/main/README.md" }
  },
  "vars": { "PACKAGE_NAME": "my-lib" },
  "readme": "# my-lib\n\nHello!\n"
}

API server endpoints

# Health
curl http://localhost:8787/health

# Version
curl http://localhost:8787/version

# Scaffold (Bearer token optional if server started with --token)
curl -H "Authorization: Bearer mysecret" -H "Content-Type: application/json" \
  -X POST http://localhost:8787/scaffold?dir=my-lib \
  -d '{
    "name": "my-lib",
    "version": "0.1.0",
    "filesMap": {
      "index.js": "module.exports = () => 'hello';\n"
    }
  }'

# Clean
curl -H "Authorization: Bearer mysecret" -H "Content-Type: application/json" \
  -X POST http://localhost:8787/clean -d '{"dir":"./out/my-lib"}'

Publish to npm

  1. Log in:
npm login
  1. Optionally change the package name in package.json if the name is taken.

  2. Publish (public):

npm publish --access public

Uninstall / revert

  • Remove generated package: delete the folder or use npmmaker --clean <dir>.
  • Uninstall the CLI from your machine:
npm uninstall -g npm-package-maker-lite

License

MIT