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

@aolyang/eslint-config

v0.0.0-beta.19

Published

```js // eslint.config.mjs for react project import globals from "globals"

Readme

Opinionated ESLint Configs

// eslint.config.mjs for react project
import globals from "globals"

import { combine, combineGlobals, ignores } from "@aolyang/eslint-config"
import react from "@aolyang/eslint-config/react"
import stylistic from "@aolyang/eslint-config/stylistic"

export default combine(
    combineGlobals(
        globals.browser,
        globals.node
    ),
    react(),
    stylistic(),
    { ignores }
)

That's All

opinionated part can be overridden

Each @aolyang/eslint-config/xxx export a default function which with opinionated config presets
The rest of the exports are also exported through @aolyang/eslint-config

Which means those are equal:

import { combine } from "@aolyang/eslint-config"
import typescript from "@aolyang/eslint-config/typescript"

export default combine(
    typescript({
        files: ["*.ts", "*.tsx"],
        rules: {
            // ...merged my opinionated rules behind
            "@typescript-eslint/no-unused-vars": "off"
        }
    })
)
import { combine, typescript, typescriptRules } from "@aolyang/eslint-config"
// import { typescript, typescriptRules } from "@aolyang/eslint-config/typescript"

export default combine(
    // this provide parser config only
    typescript({
        files: ["*.ts", "*.tsx"]
    }),
    // ...merged my opinionated rules behind
    typescriptRules({
        files: ["*.ts", "*.tsx"],
        rules: {
            "@typescript-eslint/no-unused-vars": "off"
        }
    })
)
import { combineConfig } from "@aolyang/eslint-config"
import { typescript, typescriptRules } from "@aolyang/eslint-config/typescript"

export default combineConfig({
   files: ["*.ts", "*.tsx"]
})(
    typescript(), // +++ add files
    // ...merged my opinionated rules behind
    typescriptRules({ // +++ add files
        rules: {
            "@typescript-eslint/no-unused-vars": "off"
        }
    })
)