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

pacmod-cli

v0.5.1

Published

A package module development environment tool

Downloads

58

Readme

pacmod - A package module environment

pacmod is a package module environment that can be used to develop browser modules with es6. Using babel and browserify, pacmod will compile your packages into a single distribution file.

Warning: Please note that releases before 1.0.0 may not be backwards compatable

Setup

Simply install the cli

npm install -g pacmod

And you can get started!

Package Structure

Packages are defined as self contained components or module packs that are distributed with their own unit tests. Each package should be independant and have no dependencies outside of itself. The package folder structure is

- /package-name
--- /lib
----- /index.js (entry point)
--- /tests
--- /readme.md (optional)

Project Setup

Assuming your project is organized in package-module structure you can get started by simply running

pacmod

In the project directory. pacmod will look for a packages folder and compile all packages present. You should always define a main entry point that will be invoked once the file is loaded (defaults to the main.js package)

pacmod will also copy files in the public folder of your project to the dist folder. Once complete, pacmod will open your projects dev environment in your default browser. pacmod will continue watching your files for changes and reloading them in the browser.

Configuration

To configure pacmod, create a pacmod.json file in your project directory. The following configuration options are available:

temp_folder

Default: '_build' The directory to use for temporary build files. You should have this directory in your project's .gitignore

package_name

Default: Package.json.name ('pacmod' if not available) The name of your module and the subsequent file to be built

build_target

Default: 'dist' The folder to to build the application to

script_path

Default: '' The folder relative to the BUILD_TARGET that the compiled JS file should be moved to

main_package

Default: 'main' The name of the package that should be used as the main entry point for the application. This file will be invoked on script load.

port

Default: 4000 The port to serve development files from.

test_port

Default: 4001 The port to serve test files from

Testing

pacmod has QUnit support built in! You can write all of your tests in the /tests folder of the respective package. To run your tests, run

pacmod test

from your project directory. Your tests will be built and a window will open in your default browser to run the tests. You can even run pacmod and pacmod test simultaneously while developing.