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

lazy-eslint

v0.2.1

Published

npm

Readme

Lazy ESLint

A complete sane ESLint config for lazy people for modern web.

Usage

In eslint.config.js do:

import getConfig from 'lazy-eslint'
export default getConfig()

Rationale

Oxlint and Biome do exist, sadly neither is as realiable as ESLint yet. I also rely on Sonar for all of my projects and they provide their own plugin, which is nice. All in all, ESLint just works, it is just annoying to configure, which is why this project exists.

Rules

  • Recommended via @eslint/js.
  • Standard Style, based on this.
    • But why Standard? Because it works and I do not want to maintain or create another bloody standard.
    • But why not Neostandard? Because they are not able to sort out ESLint 10 support for ages; it messes with dependabot and requires overrides for a clean npm audit.
  • Sonar via eslint-plugin-sonarjs, because pretty much every enterprise app I worked on requires Sonar compliance.
  • Additional JSON validation via eslint-plugin-jsonc, because JSON files do exist.
  • Everything in .gitignore is excluded.