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

@tsslint/compat-eslint

v3.1.4

Published

Adapter that lets ESLint rules run under TSSLint. Consumed by `importESLintRules` from [`@tsslint/config`](../config).

Readme

@tsslint/compat-eslint

Adapter that lets ESLint rules run under TSSLint. Consumed by importESLintRules from @tsslint/config.

Usage

npm install @tsslint/compat-eslint --save-dev
npm install @typescript-eslint/eslint-plugin --save-dev   # for @typescript-eslint/* rules
import { defineConfig, importESLintRules } from '@tsslint/config';

export default defineConfig({
  rules: {
    ...await importESLintRules({
      'no-unused-vars': true,
      '@typescript-eslint/no-explicit-any': 'warn',
    }),
  },
});

For each <plugin>/<rule> you reference, install the matching eslint-plugin-<plugin> (or @scope/eslint-plugin) package.

See the root README for full interop notes, including TSLint and TSL.


The rest of this file is for tsslint maintainers — internal architecture, debug knobs. Surface API consumed by @tsslint/config is just convertRule; everything else is implementation detail without API-stability guarantees.

Debug environment variables

Both flags below are read once at module load (when @tsslint/compat-eslint is first require/import-ed). Setting them later — e.g. inside a Vitest beforeAll after the module has been imported — has no effect. Set them in the shell or in your CI workflow before invoking node / tsslint.

TSSLINT_STRICT_GENERIC=1

Makes convertChildInner's GenericTSNode safety-net fall-through THROW GenericTSNodeFallbackError instead of silently producing a phantom 'TS<KindName>' ESTree node. Combine with the test suite (or your own bench fixtures) to detect any TS SyntaxKind that slips past the explicit handlers.

TSSLINT_STRICT_GENERIC=1 npm run lint

Production runs should leave it UNSET — the GenericTSNode fall-back is the safety net for unknown future TS SyntaxKind values, paired with the _parent non-enumerable defense in LazyNode so phantom nodes never trigger the visitor's stack-overflow recursion path.

TSSLINT_DEBUG_ESTREE=1

Enables instance-construction counters in lazy-estree. Reads back via getNodeTypeCounts() / getNodeTypeSourceCounts() on globalThis (so the counter is shared across require() instances of the module). Used by tsslint's own conversion-cost benchmarks.