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 🙏

© 2024 – Pkg Stats / Ryan Hefner

ppjg

v1.0.0

Published

Remove development bloat form your published package.json

Downloads

5

Readme

Publish Package JSON Generator

GitHub Workflow Status npm NPM

Generate a dedicated package.json for publishing without development bloat.

  • Only include properties you need for publishing
  • Override development values
  • Addition of new properties

Quick Start

  • Install the ppjg as a development dependency
node i -D ppjg
  • Create a new publish config called ppj.config.js in your project root directory
  • Define which package.json keys to persist and which to override:
module.exports = {
  persist: ['author', 'dependencies'],
  alter: {
    version: process.env.VERSION
  }
};
  • Run ppjg by executing the generatePublishPackageJson function or by executing the binary via Node
VERSION='V1' npx ppjg
  • Generated example ./out/package.json
{
  "author": "John Doe",
  "dependencies": {
    "example": "1.0.0"
  },
  "version": "V1"
}

Configuration

The Publish-Configuration

The publish-configuration defines which properties of the projects package.json are kept and which will be overwritten. By default, the publish-configuration is defined inside the ppj.config.js. To provide a differently named configuration, see the Generator Configuration section.

Property | Description | Config Property ---------|-------------|---------------- persist| An array of property names which will be kept inside the publish-configuration| { persist: ['author', 'name'] } alter | An object of new or altered properties and their values| { alter: { bin: './cli.js' } }

The Generator Configuration

Property | Description | CLI Flag | Config Property ---------|-------------|----------|---------------- Output Directory|Defines the location of the generated package.json|-o, --outDir DIRECTORY|{ outDir: DIRECTORY } Publish Config File|File name of the config used for the generation|-c, --config FILE|{publishConfigFileName: FILE}

Usage

Binary

The provided binary offers easy invocation via the CLI or NPM script.

CLI

  • Directly execute the binary with npx:
npx ppjg [options]

NPM script

  • Create a new script entry invoking the binary:
{
  "scripts": {
    "generatePPJ": "ppjg [options]"
  }
}
  • Run the script:
npm run generatePPJ

Programmatically

  • It is also possible to invoke the generator function directly:
import { generatePublishPackageJson, GeneratorConfigModel } from 'ppjg';

const config: Partial<GeneratorConfigModel> | undefined = { /* optional config data */ }

generatePublishPackageJson(config);