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

@kkingsbe/eslint-config

v1.0.84

Published

This is my personal ESLint configuration with fairly strict rules for TypeScript projects. This config enforces code quality standards, documentation requirements, and maintainability best practices.

Readme

@kkingsbe/eslint-config

This is my personal ESLint configuration with fairly strict rules for TypeScript projects. This config enforces code quality standards, documentation requirements, and maintainability best practices.

Features

  • TypeScript Support: Full TypeScript linting with recommended type-checked rules
  • Code Quality: SonarJS rules for detecting bugs and code smells
  • Documentation: JSDoc enforcement for all public functions, classes, interfaces, and type definitions
  • Code Formatting: Prettier integration for consistent code style
  • Complexity Limits: Enforced limits on function length, nesting depth, and file size
  • Node.js & Jest: Configured for Node.js and Jest testing environments

Installation

npm install --save-dev @kkingsbe/eslint-config

Usage

Create an eslint.config.js file in your project root:

import config from '@kkingsbe/eslint-config';

export default config;

Or extend it with your own rules:

import kyleConfig from '@kkingsbe/eslint-config';

export default [
  ...kyleConfig,
  {
    rules: {
      // Your custom rules here
    },
  },
];

Required Peer Dependencies

Make sure you have these dependencies installed:

npm install --save-dev eslint typescript

Optional Peer Dependencies

If using this config with Angular, you will need to run the following:

npm install -d angular-eslint

Configuration Details

Included Plugins & Configs

  • @eslint/js: ESLint recommended rules
  • typescript-eslint: TypeScript-specific linting with type checking
  • eslint-plugin-sonarjs: Code quality and bug detection rules
  • eslint-plugin-jsdoc: JSDoc documentation enforcement
  • eslint-plugin-prettier: Code formatting integration

Key Rules

  • JSDoc Required: All public functions, classes, interfaces, type aliases, and enums must have JSDoc comments
  • Function Length: Maximum 70 lines per function (excluding blank lines and comments)
  • Nesting Depth: Maximum 3 levels of nesting
  • File Length: Maximum 300 lines per file
  • TypeScript: Relaxed no-explicit-any, but warns on floating promises and unsafe arguments

Environment Support

  • Node.js globals
  • Jest testing framework globals
  • CommonJS module system

TypeScript Configuration

This config expects a tsconfig.json file in your project root. The TypeScript parser will use project service for type-aware linting.

License

ISC


This is Kyle's (@kkingsbe) personal ESLint configuration. Feel free to use it as a starting point for your own projects!