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

lintmesh

v0.1.3

Published

Run multiple linters in parallel with unified output

Readme

lintmesh

npm version license node

Run multiple linters in parallel. Get unified output.

ESLint taking 15 seconds while oxlint finishes in 50ms? Run them simultaneously and save time. lintmesh orchestrates your linters and merges their output into a single, consistent format.

lintmesh demo

Features

  • Parallel execution - All linters run concurrently
  • Unified output - Consistent format across eslint, oxlint, tsc, biome
  • Zero config - Uses your existing linter configs
  • CI-friendly - Clean output when piped, spinners when interactive
  • LLM-optimized - Compact format perfect for AI coding assistants

Installation

npm install -g lintmesh

Requires Node 22+ and your linters installed locally (eslint, oxlint, typescript, biome).

Usage

lintmesh                          # lint project (uses config or defaults)
lintmesh src/                     # lint directory
lintmesh src/foo.ts src/bar.ts    # lint specific files
lintmesh --linters=eslint,tsc     # select linters
lintmesh --json                   # full JSON output
lintmesh --fix                    # auto-fix where possible

Interactive Mode

When running in a terminal, lintmesh shows live progress with spinners:

✓ eslint (2.1s)
✓ oxlint 3 issues (48ms)
⠸ tsc...

When piped or in CI, output is clean with no progress noise.

Output

Default compact format (great for humans and LLMs):

src/api/user.ts:42:5 error eslint/no-unused-vars: 'result' is defined but never used.
src/api/user.ts:87:12 warning tsc/TS6133: 'options' is declared but never used.

2 issues (1 error, 1 warning)

JSON format (--json) for tooling:

{
  "cwd": "/project",
  "durationMs": 2847,
  "linters": [
    {"name": "eslint", "version": "9.39.2", "success": true, "durationMs": 2100},
    {"name": "oxlint", "version": "0.16.6", "success": true, "durationMs": 48},
    {"name": "tsc", "version": "5.7.2", "success": true, "durationMs": 890}
  ],
  "issues": [...],
  "summary": {"total": 2, "errors": 1, "warnings": 1, "fixable": 1}
}

Configuration

Create lintmesh.jsonc in your project root:

{
  "linters": {
    "eslint": { "enabled": true },
    "oxlint": { "enabled": true },
    "tsc": { "enabled": true },
    "biome": { "enabled": false }
  },
  "include": ["src/**/*.ts", "src/**/*.tsx"],
  "exclude": ["**/*.test.ts", "**/node_modules/**"],
  "failOn": "error",
  "timeout": 30000
}

Generate config automatically:

lintmesh init

Why lintmesh?

| Scenario | Without lintmesh | With lintmesh | |----------|------------------|---------------| | Run 3 linters | Sequential: 15s + 3s + 2s = 20s | Parallel: 15s | | Parse output | 3 different formats | 1 unified format | | CI logs | Mixed progress/errors | Clean, parseable | | LLM context | Send 3 outputs | Send 1 output |

Options

--json              Output full JSON (default: compact format)
--pretty            Pretty-print JSON
--fix               Auto-fix issues where possible
--linters <list>    Comma-separated: eslint,oxlint,tsc,biome
--fail-on <level>   Exit threshold: error|warning|info (default: error)
--timeout <ms>      Per-linter timeout (default: 30000)
--quiet             Suppress all progress output
--verbose           Show config file path and commands

Exit Codes

  • 0 - No issues at or above --fail-on threshold
  • 1 - Issues found
  • 2 - Execution error

License

MIT