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

@couds/eslint-config

v1.0.0

Published

Shared ESLint 10 flat config for React and Node.js projects with Prettier integration. These are the rules I use across my personal projects.

Readme

@couds/eslint-config

Shared ESLint 10 flat config for React and Node.js projects with Prettier integration. These are the rules I use across my personal projects.

Requirements

  • ESLint 10+ (flat config format)
  • ESM project — your eslint.config.js must use import/export

Installation

npm install --save-dev @couds/eslint-config eslint @eslint/js

eslint and @eslint/js are peer dependencies that your project must provide. typescript is bundled automatically (required internally by @eslint-react).

Usage

React

// eslint.config.js
import reactConfig from '@couds/eslint-config/react';

export default [
  ...reactConfig,
  // project-specific overrides
];

Node.js

// eslint.config.js
import nodeConfig from '@couds/eslint-config/node';

export default [
  ...nodeConfig,
  // project-specific overrides
];

The default export (@couds/eslint-config) is an alias for the React config.

What's included

Both configs

  • @eslint/js recommended — ESLint core rules baseline
  • eslint-plugin-import-x recommended — import/export correctness (ESLint 10-native fork of eslint-plugin-import)
  • eslint-plugin-prettier — runs Prettier as an ESLint rule (prettier/prettier: error)
  • eslint-config-prettier — disables ESLint rules that conflict with Prettier formatting

React only

  • @eslint-react/eslint-plugin recommended — React and hooks correctness rules built for ESLint 10
  • eslint-plugin-jsx-a11y recommended — accessibility rules for JSX
  • Browser + Node globals, JSX parsing enabled

Node only

  • Node globals only, no JSX

Notable rule overrides shared by both: arrow-body-style is enforced (always); no-console, max-len, no-underscore-dangle, class-methods-use-this, and several import-x style rules are disabled.

Notes

  • Flat config only — .eslintrc.* files are not supported
  • The Airbnb config base and react/function-component-definition style rule were removed during the ESLint 10 migration