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

jizy-packer

v2.1.47

Published

CLI app to generate optimized builds.

Readme

jizy-packer

A CLI tool and Node.js library to generate optimized builds for your projects. It provides utilities for configuration management, build orchestration, and file operations.

Features

  • Command-line interface for building projects (init & build)
  • Configurable via JSON and programmatic API
  • Utilities for cleaning build folders and managing configs
  • Rollup-based build process with plugin support
  • When the name of the build is "example"
    • mirrors the base example-base folder (no override)
    • moves the content of build/example to the example folder

Create a jPacker

Start by creating a new folder for your project:

mkdir my-project
cd my-project

Optionaly create a me.json file to define the default values for your projects. You can use the same file as a reference in your own projects.

keywords will prepend the keywords array in your package.json & composer.json files. gitAccount is your Git account or organization name. gitPrefix is a prefix for your Git repositories. authorName, authorEmail, authorWebsite are your personal information. homepagePrefix is the prefix for your projects homepage URL. (homepage will be https://mywebsite.com/module-alias)

{
  "keywords": ["johndoe"],
  "gitAccount": "your-account",
  "gitPrefix": "your-prefix",
  "authorName": "John Doe",
  "authorEmail": "[email protected]",
  "authorWebsite": "https://john-doe.com",
  "homepagePrefix": "https://john-doe.com/your-project",
  "license": "MIT"
}

Init your NPM package:

npm init -y

Init your Git repository:

git init

Init the Packer for your project:

npm install jizy-packer
node ./node_modules/jizy-packer/cli/init.js

Questions during the process

The init script will ask you several questions to configure your project. You can set default values in the me.json file to pre-fill some questions.

Module

Needed to build package.json, import statements, etc.

Name Name of your module to be called ex: ModuleName -> const myModule = new ModuleName();

Alias Name of your NPM package ex: new-module-name -> import ModuleName from 'module-name';

Git Repo

Needed to build repository URLs in package.json and composer.json

Git Module Your Git module name in the format "account/repo" ex: your-account/new-module-name

Account Your Git account or organization name ex: your-account

Repository Name of your Git repository ex: new-module-name

Author

(Optional) Used to build author information in package.json and composer.json

Name Your full name ex: John Doe

Email Your email address ex: [email protected]

Website Your personal or company website ex: https://your-website.com

Miscellaneous

(Optional) Additional information for your package.json and composer.json

Description A brief description of your package

Keywords Comma separated keywords for your package ex: jizy,jdz,example,packer -> "keywords": [ "jizy", "jdz", "example", "packer" ]

Homepage Your project homepage URL ex: https://your-website.com/new-module-name

Build your project

CLI

node ./cli/jpack.js --debug
node ./cli/jpack.js --action build --name perso --config {"key":"value"}
node ./cli/jpack.js --action build --name perso --config ABSOLUTE_PATH_TO_JSON_FILE

Options:

  • --action, -a Build action (dist|build)
  • --name, -n Name of the build
  • --config, -c Path to the custom config file or JSON string
  • --debug, -d Enable debug mode

Programmatic

import { jPackBuild } from 'jizy-packer';

await jPackBuild({
	action: 'build',
	name: 'perso',
	config: 'PATH_TO_JSON_FILE',
	debug: true
});

Development

Run the example to test the full pipeline (scaffold + build):

npm run example

This creates a dummy "MyWidget" package in examples/output/, builds it with jizy-packer, and verifies the output.