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

@litsx/eslint-plugin

v0.3.0

Published

Official ESLint processor support for LitSX-authored syntax

Readme

@litsx/eslint-plugin

npm Release Module Provenance

Official ESLint support for LitSX-authored syntax.

This package is processor-first:

  • LitSX-authored source is virtualized before ESLint parses it
  • ESLint findings are remapped back to original authored positions
  • LitSX-specific semantic rules run with normal ESLint ruleIds

It does not ship a dedicated LitSX parser.

Installation

npm install -D eslint @litsx/eslint-plugin

Flat Config

import litsx from "@litsx/eslint-plugin";

export default [
  litsx.configs["recommended-flat"],
];

Other shipped flat presets:

  • litsx.configs["recommended-lint-flat"]
  • litsx.configs["recommended-react-migration-flat"]
  • litsx.configs["strict-flat"]

Classic Config

{
  "extends": ["plugin:@litsx/recommended"]
}

Other shipped classic presets:

  • plugin:@litsx/recommended-lint
  • plugin:@litsx/recommended-react-migration
  • plugin:@litsx/strict

recommended is the editor-friendly baseline:

  • LitSX source is processed correctly
  • it avoids duplicating inline feedback that @litsx/typescript-plugin already shows in editors
  • it disables the processor's baseline authored diagnostics too

Use recommended-lint when you want ESLint itself to enforce the LitSX semantic rules in CI or editor linting.

Included Rules

Shipped in recommended-lint:

  • @litsx/no-native-classname
  • @litsx/no-invalid-binding-value
  • @litsx/no-unknown-binding
  • @litsx/static-hoists-top-level
  • @litsx/no-duplicate-static-hoist
  • @litsx/no-react-memo
  • @litsx/no-react-compat-surface
  • @litsx/prefer-destructured-props
  • @litsx/no-opaque-prop-metadata-inference
  • @litsx/require-top-level-hoists-first
  • @litsx/no-unknown-static-hoist

Autofix

The plugin only autofixes safe, unambiguous cases.

Today that means:

  • className -> class on native LitSX intrinsic elements

Notes

  • The plugin is designed to work with LitSX-authored forms such as @click, .value, ?disabled, and static styles = ....
  • Processor mode means lint messages are reported on the original source even though ESLint parses a virtualized version internally.
  • Prettier support is still a separate gap; this package only covers linting.