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 🙏

© 2025 – Pkg Stats / Ryan Hefner

pure-publish

v1.0.1

Published

Publish with a pure package.json

Readme

Pure-Publish

Publish node packages with a purified 'package.json'

Install

npm install pure-publish -D

Usage

pure-publish [command]

Command publish

This is the default command.

A tarball is created and published to the registry using the command

npm publish <tarball>

The tarball is deleted after running npm publish.

Command pack

A tarball file of the package is created. The file 'package.json' inside of this tarball is purified.

Command pure

The file 'package.json' is purified. The original file is copied to 'package.json.backup'.

Command restore

The file 'package.json' is restored from a previously saved backup - see command pure above. The backup file is deleted.

Command run <cmd>

After 'package.json' is purified the specifed <cmd> is executed. Afterwards the original version of 'package.json' is restored.

Options

--suffix <sfx>

Instead of 'package.json.backup' the backup file will be named 'package.json<sfx>'

--tarball <path>

Alternative path for the generated tarball. If the file name is '*' it will be replaced by the standard name. For example:

pure-publish pack --tarball "./.pack/*"

--dry-run

Do nothing - show only what would be done. Also dump the purified version of 'package.json'.

Configuration

The configuration is read from the key 'pure-publish' of 'package.json' or from the file 'pure-publish.config.json'. Example:

{
   "suffix": ".bak",
   "tarball": "./.pack/*",
   "indent": 2,
   "remove": [
       "devDependencies",
       "pure-package",
       "files"
   ],
   "replace": {
       "scripts": {
           "test": "echo \"No tests defined!\" && exit 1"
       }
   }
}

Possible keys are:

suffix

Type: string

Same as option --suffix.

tarball

Type: string

Same as option --tarball.

indent

Type: string | number

Indentation of the purified 'package.json' - default 2.

remove

Type: string[]

The keys specified in remove are removed from 'package.json'

replace

Type: object

The contents of 'package.json' are combined with the object.