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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@kasoa/eslint-config

v0.0.12

Published

Kasoa's ESLint config

Downloads

736

Readme

@kasoa/eslint-config

Kasoa's ESLint config

Installation

Install ESLint and the config:

pnpm add -D @kasoa/eslint-config eslint

Note: Requires Node.js >=24 and a TypeScript setup.

Usage

Import the desired config in your eslint.config.ts (using ESLint's flat config format). Extend it with project-specific overrides as needed.

React Projects

export { react as default } from "@kasoa/eslint-config/react";

Node.js Projects

export { node as default } from "@kasoa/eslint-config/node";

Base Config

export { base as default } from "@kasoa/eslint-config/base";

Custom Overrides

Use defineConfig to add project-specific rules:

import { node } from "@kasoa/eslint-config/node";
import { defineConfig } from "eslint/config";

export default defineConfig(node, {
  rules: {
    "no-console": "warn",
  },
});

Configurations

  • base: Core rules for TypeScript, imports, code quality, and testing.
  • node: Extends base with Node.js-specific rules.
  • react: Extends base with React-specific rules.

All configs use Prettier-compatible rules and enforce strict standards.

Contributing

  • Follow project conventions.
  • Test changes in a sample project.
  • Update this README for new configs.

Author

Emmanuel Chucks https://github.com/emmanuelchucks

License

MIT