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

@pilotlint/plugin-changes

v0.2.4

Published

pilotlint rules for files that must or must not change together.

Readme

@pilotlint/plugin-changes

npm

pilotlint rules for changes: files that must change together, and generated files that must not be edited by hand. The rules compare the working tree with a git ref, HEAD by default.

Install

npm install -D pilotlint @pilotlint/plugin-changes

Use

// pilotlint.config.ts
import changes from '@pilotlint/plugin-changes';
import { defineConfig } from 'pilotlint';

export default defineConfig({
  plugins: [changes],
  rules: {
    'changes/requires-change': [
      'error',
      {
        rules: [
          {
            when: 'src/**/messages.ts',
            require: 'src/translations/en.json',
            hint: 'Run pnpm extract-intl.',
          },
        ],
      },
    ],
    'changes/no-manual-edit': [
      'error',
      {
        rules: [{ files: 'src/generated/**', unless: 'schema.graphql', hint: 'Run pnpm codegen.' }],
      },
    ],
  },
});

In CI, compare with the main branch: pilotlint check --base origin/main.

Rules

| Rule | Checks | | ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | requires-change | When some files change, the files that depend on them change too | | no-manual-edit | Generated files change only together with the input they come from |

See all options, or run pilotlint rules explain changes/<rule>.

License

MIT