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

prodbuild

v1.7.0

Published

Simple and fast packager and development tool for no-framework websites.

Readme

Prodbuild

npm

Easy-to-use minifier, dev server, and work-in-progress bundler for no-framework websites. Also partially an experimentation in compliation, transpilation, minification, bundling, and general site building/packaging.

Install

npm i --save-dev prodbuild

Documentation

build.config.json

This is Prodbuild's config file. The location of this file is considered the project root folder.

Parameters:

  • entry: string: the path, relative to the project root folder, to the folder containing all source files.
  • output: string: the path, relative to the project root folder, to the folder to emit all processed files to
  • port: integer: specify the port for the dev-server
  • exclude: Array<string>: exclude folders and files, written as an array of strings (ex: ["file.html", ".txt", "images/"] excludes the file called file.html, all ".txt" files, and all files in the folder "images")

Default values:

{
    "entry:": "./src/",
    "output:": "./dist/",
    "port": 5000,
    "exclude": [".ts"]
}

TypeScript Support

Do not specify an outFile or outDir. Prodbuild will automatically run tsc on every build. The builder will then take the emitted JavaScript files and treat them as normal JavaScript files. .ts files will by be excluded from the project during building.

When using the dev server, Prodbuild will run tsc on server start and fetch the compiled JavaScript files accordingly. Note: Any following changes made to TypeScript files will require the user to run tsc manually. This will be made automatic in the next update (v1.7.1).

Note

As of version 1.7.0, script elements that import a .ts file will not resolve to a compiled .js file.

Commands

npx prodbuild build

Minifies and uglifies all HTML, CSS, and JS/TS files in the specified entry folder (default is './src/') and emits all files to the specified output folder (default is './dist/').

See the above section for information regarding entry and output folders.

Note: TypeScript files are transpiled as part of the build process.

npx prodbuild serve

Arguments
  • start: start the dev server at the specified port (default is 5000). This will open in the folder specified in config.entry unless used with --prod (see below)
  • kill: stop the dev server
Options:
  • --prod: starts the dev server in the production (output) directory
  • --purge: purge all messages in .prodbuildrc/log.txt

npx prodbuild init

Create a build.config.json file and setup the corresponding folders.