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

@fledra/eslint-config

v3.0.2

Published

One opinionated config for ESLint

Readme

@fledra/eslint-config

NPM Version

One opinionated config for ESLint.

This config is a refactored/modified version of Anthony Fu's ESLint config. I will not copy every change from his config but I might occasionally yoink the ones I like.

  • ESLint Flat config format
  • Respects .gitignore by default
  • Code style: Minimal for reading, stable for diff, consistent... enough.

Usage

Install

First install eslint and this config:

pnpm i -D eslint @fledra/eslint-config

And create eslint.config.mjs in your project root:

// eslint.config.mjs
import fledra from '@fledra/eslint-config';

export default fledra();

Add script for package.json

For example:

{
  "scripts": {
    "lint": "eslint",
    "lint:fix": "eslint --fix"
  }
}

Customization

I followed Anthony's config for the most part so configuration options are pretty much the same. Check out customization section of his config for more info.

Important notes about configuration

  • type key does not exist in the configuration object

Plugins Renaming

I thought I did not want any plugin renaming at first but only kept the original name of @typescript-eslint, which was confusing.

From version 2.0.0 onwards plugin renaming is enabled by default.

| New Prefix | Original Prefix | Source Plugin | | ---------- | ---------------------- | ------------------------------------------------------------------------------------------ | | import/* | import-lite/* | eslint-plugin-import-lite | | node/* | n/* | eslint-plugin-n | | yaml/* | yml/* | eslint-plugin-yml | | ts/* | @typescript-eslint/* | @typescript-eslint/eslint-plugin | | style/* | @stylistic/* | @stylistic/eslint-plugin |

When you want to override rules, or disable them inline, you need to use the new prefix:

-// eslint-disable-next-line @typescript-eslint/consistent-type-definitions
+// eslint-disable-next-line ts/consistent-type-definitions
type foo = { bar: 2 }

Change back to original prefix

If you really want to use the original prefix, you can revert the plugin renaming by:

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

export default fledra()
  .renamePlugins({
    ts: '@typescript-eslint',
    yaml: 'yml',
    node: 'n'
    // ...
  });

License

MIT License © 2025-PRESENT Baran D. (Fledra)