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

@matrixai/lint

v0.2.12

Published

Org wide custom eslint rules

Readme

js-lint

A batteries-included, TypeScript-aware linting CLI and ESLint flat config bundle for use in Matrix AI JavaScript/TypeScript projects.

  • Type-aware linting powered by @typescript-eslint using one or more tsconfig.json files
  • Built-in support for React, Tailwind, JSX a11y, Prettier, and Matrix AI custom rules
  • Supports Prettier formatting for Markdown and ShellCheck for shell scripts
  • Single command to lint JavaScript/TypeScript, Markdown, and shell scripts
  • Customizable via matrixai-lint-config.json and extensible with your own ESLint config
  • CLI options to override config and enable auto-fix

Installation

npm install --save-dev @matrixai/lint

Usage

matrixai-lint

To run with autofix:

matrixai-lint --fix

CLI Options

| Flag | Description | | ----------------- | ---------------------------------------------------------------------------- | | (no flag) | Uses built-in Matrix AI ESLint config | | --fix | Enables auto-fixing via ESLint and Prettier | | --user-config | Uses detected `eslint.config.[js,mjs,cjs,ts] from the project root if found | | --config <path> | Explicitly use a custom ESLint config file |

Examples

matrixai-lint --fix
matrixai-lint --user-config
matrixai-lint --config ./eslint.config.js --fix

TypeScript Support

The linter is TypeScript-aware and requires a tsconfig.json to determine which files to lint and how to parse them.

By default:

  • It looks for tsconfig.json in the project root
  • Files are selected based on the include and exclude fields in the tsconfig

Working with multiple tsconfigs

If your project uses more than one tsconfig.json or doesn't have one at the root, you can configure the linter using a matrixai-lint-config.json file at the root:

{
  "tsconfigPaths": ["./tsconfig.base.json", "./packages/core/tsconfig.json"],
  "forceInclude": ["scripts", "src/overrides"]
}

| Field | Type | Description | | --------------- | ---------- | ---------------------------------------------------------------------------------------- | | tsconfigPaths | string[] | One or more paths to tsconfig.json files | | forceInclude | string[] | Paths to always include, even if excluded by tsconfig (must be included by at least one) |

⚠ If a path in forceInclude is not included in any of the tsconfigPaths, TypeScript will throw a parsing error.

ESLint Config Override

You can use your own ESLint config by one of the following methods:

1. Inline Custom Config

matrixai-lint --config ./eslint.config.js

2. Auto-detect with --user-config

matrixai-lint --user-config

This will look for a valid eslint.config file in the project root.

Valid config filenames:

  • eslint.config.js
  • eslint.config.cjs
  • eslint.config.mjs
  • eslint.config.ts

3. Extend the base config

// eslint.config.js
import matrixai from '@matrixai/lint/config';

export default [
  ...matrixai,
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'error',
      'no-console': 'off',
    },
  },
];

Development

Run nix develop, and once you're inside, you can use:

# install (or reinstall packages from package.json)
npm install
# build the dist
npm run build
# run the repl (this allows you to import from ./src)
npm run tsx
# run the tests
npm run test
# lint the source code
npm run lint
# automatically fix the source
npm run lintfix

Docs Generation

npm run docs

See the docs at: https://matrixai.github.io/js-lint/

Publishing

Publishing is handled automatically by the staging pipeline.

Prerelease:

# npm login
npm version prepatch --preid alpha # premajor/preminor/prepatch
git push --follow-tags

Release:

# npm login
npm version patch # major/minor/patch
git push --follow-tags

Manually:

# npm login
npm version patch # major/minor/patch
npm run build
npm publish --access public
git push
git push --tags