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

packlint

v0.2.4

Published

> Organize `package.json` in a large monorepo.

Downloads

5,581

Readme

packlint

Organize package.json in a large monorepo.

Install

npm install --dev packlint

or with yarn

yarn install --dev packlint

Usage

Packlint has two main features now. Sort package.json in custom order (or recommended order by default). Add or modify fields by applying merge rule. (ex: if you want to change build script of all packages in your large monorepo)

  Usage
    $ packlint

  Options
    --recursive,-R            Apply packlint to all sub-packages in repo recursively

  Commands
    (default)                 Apply all rules in config
    merge                     Apply merge rules in config
    sort                      Apply order rules in config

  Examples
    $ packlint
    $ packlint -R
    $ packlint merge
    $ packlint merge -R
    $ packlint sort
    $ packlint sort -R

Configuration

The Packlint configuration file is named packlint.config.mjs. It should be placed in the root directory of your project and default export configuration object. For example:

// packlint.config.mjs
export default {
  files: ['./packages/**/package.json'],
  ignores: ['./package.json'],
  rules: {
    merge: {
      type: 'module',
      scripts: {
        prepack: 'yarn build',
        build: 'rm -rf dist && tsup ./src/index.ts --format esm --dts',
        dev: 'yarn run build --watch',
        typecheck: 'tsc --noEmit',
      },
      publishConfig: {
        access: 'public',
      },
    },
  },
};

Configuration Object

  • files - An array of glob patterns indicating package.json that the configuration object should apply to. If not specified, default to './package.json'.

  • ignores - An array of glob patterns indicating the files that the configuration object should not apply to. If not specified, the configuration object applies to all files matched by files.

  • extends - A path to the other configuration file. Only the rule will be extended and will be merge with mergeDeepRight function.

  • rules - An object containing the configured rules. When files or ignores are specified, these rule configurations are only available to the matching files.

    • order - An array of strings indicating the order of package.json keys. The sort command uses this rule to sort package.json by keys. If not specified, the recommended order will be applied by default.

    • merge - An object that is merged with package.json. The merge command uses mergeDeepRight function, and the first object is package.json, and the second one is this object.

      Creates a new object with the own properties of the first object merged with the own properties of the second object. If a key exists in both objects:

      • and both values are objects, the two values will be recursively merged
      • otherwise the value from the second object will be used.

In Package.json

  • If you set packlint: false in package.json, it will be ignored from applying packlint.