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

@blacklizard/eslint-blacklizard

v1.0.1

Published

Reusable, opinionated ESLint config — blacklizard code standards.

Readme

@blacklizard/eslint-blacklizard

Reusable, opinionated ESLint config — Blacklizard code standards. Built on eslint-config-airbnb-extended, flat config, ESLint 9+.

Install

pnpm add -D eslint @blacklizard/eslint-blacklizard

eslint is a peer dependency (>=9). Requires Node >=24.

Usage

The default export auto-configures itself — every rule set is scoped by file extension, so .js/.ts, .vue, .html, .css and .eta files each get the right rules with no manual selection:

// eslint.config.mjs — lints everything
export { default } from '@blacklizard/eslint-blacklizard';

That is all most projects need. The individual configs are also exported if you want to lint only one file type:

export { typescriptConfig as default } from '@blacklizard/eslint-blacklizard';
export { vueConfig as default } from '@blacklizard/eslint-blacklizard';
export { htmlConfig as default } from '@blacklizard/eslint-blacklizard';
export { cssConfig as default } from '@blacklizard/eslint-blacklizard';
export { etaConfig as default } from '@blacklizard/eslint-blacklizard';

To extend a config with project-specific rules:

import config from '@blacklizard/eslint-blacklizard';

export default [
  ...config,
  {
    rules: {
      // project overrides
    },
  },
];

Exports

| Export | Files | Covers | | ------------------ | ---------------- | ------------------------------------------------------------ | | autoConfig | all of the below | every config combined, scoped by file extension | | typescriptConfig | .js, .ts | airbnb base + node + typescript; Tailwind classes in JSX/TSX | | vueConfig | + .vue | above, widened to SFCs + eslint-plugin-vue + Tailwind | | htmlConfig | .html | @html-eslint recommended markup rules | | etaConfig | .eta | JS inside <% %> exec tags of Eta templates | | cssConfig | .css | @eslint/css recommended rules |

default is autoConfig.

Notable rule choices

  • @stylistic/max-len: 120 (comments + URLs exempt)
  • @stylistic/semi: always
  • max-depth: 2
  • @stylistic/padding-line-between-statements: blank lines after imports, before return, around blocks and functions
  • no-console: error (allows console.warn / console.error)
  • Relaxed rules for *.{test,spec}.* and __tests__/

Tailwind CSS

typescriptConfig and vueConfig lint Tailwind class attributes via eslint-plugin-better-tailwindcss (recommended rules — class order, duplicates, conflicts, unknown classes).

Class-resolution rules need to know your Tailwind setup, so consumers must add a settings block pointing at it:

import { vueConfig } from '@blacklizard/eslint-blacklizard';

export default [
  ...vueConfig,
  {
    settings: {
      'better-tailwindcss': {
        entryPoint: 'src/styles/app.css', // Tailwind v4: your CSS entry
        // tailwindConfig: 'tailwind.config.js', // Tailwind v3 instead
      },
    },
  },
];

tailwindcss (^3.3.0 || ^4.1.17) must be installed in the project.

Requirements & caveats

  • Typed linting (typescriptConfig, vueConfig) needs a tsconfig.json covering the linted files — including .vue for Vue projects. Without it, ESLint reports "not found by the project service".
  • Tailwind: without the settings['better-tailwindcss'] block above, class-resolution rules cannot work and will flag every class as unknown.
  • HTML: inline <script> JS is not linted — keep scripts in external .js files.
  • Eta: only JS in <% %> exec tags is linted. Interpolation tags (<%= %>, <%~ %>) and HTML markup are not checked.
  • CSS: css/no-invalid-at-rules is disabled — Tailwind at-rules (@apply, @theme, @utility, @variant) are not standard CSS and would otherwise false-flag every Tailwind file. All other @eslint/css rules (empty blocks, duplicate imports/keyframes, !important, baseline, etc.) stay on.

Releasing

Versioning is managed with changesets:

pnpm changeset   # 1. record a change + pick bump type (patch/minor/major)
pnpm version     # 2. apply bumps, write CHANGELOG.md     (changeset version)
git commit -am "version packages"   # 3. commit the bump
pnpm release     # 4. lint + test, then tag + push

Pushing the v* tag triggers the GitHub Actions workflow, which publishes to npm with provenance.

License

MIT

eslint