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

@acme-skunkworks/eslint-config

v1.1.2

Published

Shared ESLint flat-config preset with TypeScript, React, Astro, Sanity, and Storybook support

Readme

@acme-skunkworks/eslint-config

A shared ESLint v9 flat-config preset composer for TypeScript and React projects — import named-export presets and compose only the ones you need.

npm version Provenance: built and signed on GitHub Actions License: MIT Node engine

Every release is published to npm via OIDC Trusted Publishing with a provenance attestation — the artefact is built and signed on GitHub Actions, so consumers can verify exactly which commit and workflow produced it.

Install

pnpm add -D @acme-skunkworks/eslint-config eslint prettier

eslint (^8.57.0 || ^9.0.0) and prettier (^3.0.0) are required peer dependencies — install them alongside. Every ESLint plugin the config uses ships as a regular dependency, so you don't install plugins separately. Node 22+ is required.

ESLint v8 users: flat config isn't the default in v8 — set ESLINT_USE_FLAT_CONFIG=1 so ESLint reads your eslint.config.js. ESLint v9 uses flat config by default, so no flag is needed.

Quick start

The package exposes each preset as a named export. Compose them in your eslint.config.js:

import {
  base,
  typescript,
  frameworkRouting,
} from "@acme-skunkworks/eslint-config";

export default [
  ...base,
  typescript,
  ...frameworkRouting,
  // your overrides last so they win
  { rules: { "@typescript-eslint/no-explicit-any": "warn" } },
];

Pull in only the presets your project needs. Array presets are spread with ...; single-config presets are added as-is — the table below notes which is which.

Presets

Core — the everyday stack:

| Preset | Shape | What it covers | | ------------------ | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | base | array (...) | Plugin-alias hack, global ignores, the canonical baseline, package.json lint config, CommonJS and ESM file overrides (Node + ES globals for .cjs / .mjs so standalone scripts parse without no-undef), and the preferences block (top-level type imports, func-style: declaration, Prettier integration, import resolver, no-console warn). The "you almost always want this" stack. | | typescript | single | Overrides for **/*.{ts,tsx} — disables react/no-unused-prop-types and react/prop-types, which are redundant under TypeScript. | | frameworkRouting | array (...) | Turns off canonical/filename-match-exported for routing dirs — routes/**, app/**, pages/** (Next.js), src/routes/** (SvelteKit), src/pages/** (Astro) — and re-allows arrow functions on root.tsx / *.route.tsx. Spread after base (see Gotchas). | | testing | single | Relaxes strict TypeScript rules and import/no-extraneous-dependencies for **/*.{test,spec}.*, __tests__/**, and setup files. |

Opt-in — pull in per project:

| Preset | Shape | What it covers | | ----------------- | ------------- | ------------------------------------------------------------------------------------------------------------------- | | astro | array (...) | eslint-plugin-astro/flat/recommended plus Astro-specific overrides. | | sanity | array (...) | Schema property ordering for *.schema.ts and structure-file exceptions, for Sanity Studio projects. | | storybook | single | Overrides for **/*.stories.{ts,tsx}. | | complexity | array (...) | Raises the cyclomatic-complexity threshold to 40 for **/scripts/**, where orchestration scripts run linearly. | | e2e | single | Disables react-hooks/rules-of-hooks for **/e2e/** — Playwright test.extend callbacks are false positives. | | tableComponents | single | Disables react/no-unstable-nested-components for **/*Table.tsx — TanStack Table / Refine column-cell renderers. |

A deprecated default export still bundles the v6.x composition for back-compat during migration. New code should use the named exports above. See the migration guide.

Gotchas

Two ordering rules are easy to get wrong and fail silently — the config still loads, but the intended override never wins:

  • Spread frameworkRouting after ...base. Its func-style override must come later in the array than the preferences block (which base includes), or base wins and the React Router 7 typed-export pattern breaks.
  • frameworkRouting is an ordered pair of configs for the same reason — its second element (the React Router exceptions) must stay after its first, which in turn must follow preferences. If you ever expand the spread into individual elements, preserve their order.

Full rationale (and the protomolecule issues behind it) is in CLAUDE.md.

Links