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

@yentsun/lint

v0.1.0

Published

Opinionated ESLint plugin with custom style and correctness rules for JS/React projects

Readme

@yentsun/lint

An opinionated ESLint plugin with custom style and correctness rules for JS/React projects. A couple of rules add support for codebases split into packages or multiple runtime targets, but the plugin works in any project.

Installation

npm install --save-dev @yentsun/lint eslint eslint-plugin-react eslint-plugin-react-hooks

Requires ESLint 9+ (flat config).

Usage

JS / Node projects — built-in rules + all custom rules:

// eslint.config.js
import ytLint from '@yentsun/lint';

export default [
  ytLint.configs.recommended,
];

React projects — everything above + React plugin rules:

import ytLint from '@yentsun/lint';

export default [
  ...ytLint.configs.react,
];

Or enable individual rules:

import ytLint from '@yentsun/lint';

export default [
  {
    plugins: { '@yentsun/lint': ytLint },
    rules: {
      '@yentsun/lint/no-unused': 'error',
      '@yentsun/lint/two-blank-lines-after-imports': 'warn',
    },
  },
];

Rules

Formatting

| Rule | Description | |------|-------------| | object-curly-spacing | Spaced object braces with nested-close exception | | two-blank-lines-after-imports | Exactly two blank lines after the final top-level import | | no-blank-lines-between-declarations | No blank lines between consecutive variable declarations | | blank-line-after-if | Blank line after an if statement before the next statement | | blank-line-after-unpacking | Blank lines between leading declaration preparation phases |

Imports

| Rule | Description | Options | |------|-------------|---------| | import-general-to-specific | Import ordering by source category with alphabetical fallback | internalAliases | | no-relative-cross-package-imports | Disallow relative imports that cross package boundaries | packageRootPattern |

Variables & exports

| Rule | Description | |------|-------------| | no-unused | Report and autofix unused imports, destructured properties, and caught errors | | no-renamed-unused-destructure | Disallow destructuring renames to underscore-prefixed names |

Documentation

| Rule | Description | |------|-------------| | require-jsdoc | Require JSDoc for named/exported functions, class methods, and object methods |

Environment boundaries

| Rule | Description | Options | |------|-------------|---------| | no-process-exit-outside-cli | Disallow process.exit outside CLI files | allowedProcessExitGlobs | | no-nodejs-builtins-in-webapp | Disallow Node.js built-ins in browser code | browserCodeGlobs |

Configurable options

Rules that encode path or alias assumptions accept options so they work in any project layout:

  • internalAliases — list of bare import aliases treated as internal (e.g. ["backend", "shared"]).
  • packageRootPattern — glob identifying package roots (default: packages/*).
  • allowedProcessExitGlobs — globs where process.exit is permitted.
  • browserCodeGlobs — globs that define browser-only code boundaries.

Configs

| Config | Description | |--------|-------------| | configs.recommended | Built-in ESLint rules + all custom rules at error | | configs.react | recommended + eslint-plugin-react + eslint-plugin-react-hooks |

Development

Run the rule tests (ESLint's RuleTester on Node's built-in test runner):

npm install
npm test

License

MIT