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

eslint-plugin-yenz

v2.0.0

Published

Adds custom rules that Jens likes

Readme

eslint-plugin-yenz

Adds custom rules that Jens likes

Installation

yarn add eslint-plugin-yenz --dev

Usage

Flat Config (ESLint 8.21.0+)

// eslint.config.js
import yenz from 'eslint-plugin-yenz';

export default [
  {
    plugins: {
      yenz,
    },
    rules: {
      'yenz/type-ordering': 'error',
      'yenz/no-loops': 'warn',
    },
  },
  // Or use the recommended config
  yenz.configs.recommended,
];

Legacy Config (.eslintrc)

{
  "plugins": ["yenz"],
  "rules": {
    "yenz/type-ordering": "error",
    "yenz/no-loops": "warn"
  }
}

Rules

yenz/type-ordering

Ensures that null/undefined types are listed last in TypeScript union types.

yenz/no-loops

Disallows certain loop types (allows for...of and for...in loops).

Preset Configurations

  • recommended - Enables type-ordering as error, no-loops as warning
  • `

Release Procedure

  1. Open a new branch for your work.
  2. Make all changes in that branch.
  3. Run yarn lint and resolve any errors.
  4. Add code samples that intentionally fail your new or updated rules to confirm they are caught.
  5. Bump the version:
    • For stable releases:
      yarn version --major   # or --minor or --patch
    • For pre-releases (alpha, beta, rc):
      yarn version --prerelease --preid alpha   # or beta, rc
      # Or for specific version bumps:
      yarn version --premajor --preid alpha    # 2.1.0-alpha.1 -> 3.0.0-alpha.0
      yarn version --preminor --preid beta     # 2.1.0-alpha.1 -> 2.2.0-beta.0
      yarn version --prepatch --preid rc       # 2.1.0-alpha.1 -> 2.1.1-rc.0
    • Commit and push your changes, then open a PR.
  6. After review, merge your branch into main.
  7. Publish the package:
    • On the main branch, pull the latest changes and run:
      • For stable releases:
        yarn publish --non-interactive --access public
      • For pre-releases (alpha, beta, rc):
        yarn publish --tag beta --non-interactive --access public   # or alpha, rc
    • This will publish the version already set in package.json.
    • Do not run yarn publish before merging to main.
  8. Users can install pre-releases with:
    yarn add eslint-plugin-yenz@beta   # or @alpha, @rc
  9. Tag the release in git if desired.