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

@gurja/eslint-config

v6.0.0

Published

A simple to use ESlint configuration

Downloads

17

Readme

@gurja/eslint-config

Configuring ESLint is always annoying and can even be a nightmare sometimes. This package includes a few opinionated configs

Setup

You can install it with npm, Yarn or pnpm

# npm
npm i -D @gurja/eslint-config eslint

# Yarn
yarn add -D @gurja/eslint-config eslint

# pnpm
pnpm add -D @gurja/eslint-config eslint

Inside eslint.config.js (or eslint.config.mjs if you don't have "type": "module" on your package.json):

import { config, base } from "@gurja/eslint-config";
import react from "@gurja/eslint-config/react";

export default config(
  base(),
  react(),
  // any other ESLint config you'd want to add as well
);

Available Configs

Base

All others configs inherit from this one. It includes the ESLint recommended rules and TypeScript ESLint's recommended, strict, stylistic rules and their type checked counterparts.

Node

Includes nodejs globals and:

React

Includes browser and service worker globals, and:

Next

Includes all of React's plugins, and:

Jest

Includes jest globals, and:

Advanced Setup

Here's a kitchen sink example:

// eslint.configs.mjs
import { config, globals, base } from "@gurja/eslint-config";
import react from "@gurja/eslint-config/react";
import next from "@gurja/eslint-config/next";
import jest from "@gurja/eslint-config/jest";

// by default it uses the tsconfig.json at the same level as the eslint config file for type linting
export default config(
  base({ allowDefaultProject: ['*.config.js'] }), // allowDefaultProject can't include '**' patterns
  react({ files: ["packages/react-project/**/*.{ts,tsx}"] }),
  next({ files: ["packages/next-project/**/*.{ts,tsx,js,jsx}"] }), // next already includes react's rules
  jest({ disableTypeChecking: true, files: ["**/*.{test,spec}.{ts,tsx}"] }),
  {
    files: ["packages/jquery-app/**/*.js"],
    languageOptions: {
      globals: globals.jquery,
    },
  },
  {
    rules: {
      "react-compiler/react-compiler": "off", // customize your rules if you find it necessary
    }
  }
);