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

@theholocron/eslint-config

v7.22.0

Published

A ESLint configuration for writing well-formed Javascript within the Galaxy.

Readme

ESLint Config

A ESLint configuration for writing well-formed JavaScript and TypeScript.

Installation

pnpm add -D @theholocron/eslint-config

Install only the peer dependencies for the presets you use (all are optional except the core):

# Core (always required)
pnpm add -D @eslint/js eslint globals

# TypeScript
pnpm add -D typescript-eslint

# React
pnpm add -D eslint-plugin-react

# Next.js
pnpm add -D @next/eslint-plugin-next

# Node.js
pnpm add -D eslint-plugin-n

# Vitest
pnpm add -D @vitest/eslint-plugin

# Storybook
pnpm add -D eslint-plugin-storybook

# Cypress
pnpm add -D eslint-plugin-cypress

Usage

Individual presets

Each preset is a separate subpath import so only its plugin loads — importing base won't pull in React or Cypress plugins you don't use.

base and typescript are available from the root:

import { base, typescript } from "@theholocron/eslint-config";

export default [...base(), ...typescript()];

All other presets use subpath imports:

import { node } from "@theholocron/eslint-config/node";
import { react } from "@theholocron/eslint-config/react";
import { vitest } from "@theholocron/eslint-config/vitest";
import { next } from "@theholocron/eslint-config/next";
import { storybook } from "@theholocron/eslint-config/storybook";
import { cypress } from "@theholocron/eslint-config/cypress";

Bundles

Bundles combine presets and peer plugins into a single import for common project types. Use these when you want a ready-made config with no manual composition:

// React app (base + typescript + react + storybook + vitest)
import { reactApp } from "@theholocron/eslint-config/bundles/react-app";
export default [...reactApp()];

// Next.js app (base + typescript + react + next + vitest)
import { nextApp } from "@theholocron/eslint-config/bundles/next-app";
export default [...nextApp()];

// Node.js app or CLI (base + typescript + node + vitest)
import { nodeApp } from "@theholocron/eslint-config/bundles/node-app";
export default [...nodeApp()];

// Publishable library (base + typescript + vitest)
import { library } from "@theholocron/eslint-config/bundles/library";
export default [...library()];

Add project-specific configs after the bundle — they are merged in order:

import { reactApp } from "@theholocron/eslint-config/bundles/react-app";
import { cypress } from "@theholocron/eslint-config/cypress";

export default [...reactApp(), ...cypress(), { settings: { react: { version: "detect" } } }];

ESLint version

Requires ESLint v10. The react preset wraps eslint-plugin-react with @eslint/compat's fixupConfigRules to patch APIs removed in ESLint v10 — no extra config needed.