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

million-lint-check

v1.0.18

Published

A command-line tool to verify if Million Lint is active in a project.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

crnshcrnsh

Keywords

millionclitestingfrontend

Readme

What?

Million Lint Checker is a command line tool that automatically detects whether Million Lint works on your repository or not.

How?

It works by doing the following things -

  1. Detects package manager and does local setup using @antfu/ni
  2. Runs @million/lint
  3. Randomly interacts (fuzzes) with the frontend and detects Million Lint suggestions in the shadow DOM using puppeteer

Installation

  • Run npx million-lint-check@latest setup $PORT, where $PORT is the port your frontend will run on in development.

Note

  • For some projects setup will have to be done manually. Once the project is at a state where a simple npm run dev is sufficient to run it, this tool can be used.
  • This only works with VSCode
  • I've only tested this on the project below ;_; (should work for all nr dev projects)

Example

We'll test the CLI on crnsh/github-h-index as an example

  1. git clone https://github.com/crnsh/github-h-index.git
  2. cd github-h-index
  3. code . (This is temporarily necessary)
  4. npx million-lint-check@latest setup 3000
Running development server...
Development server started in the background.
Opening browser and interacting with components...

> [email protected] dev
> next dev

   ▲ Next.js 14.1.1
   - Local:        http://localhost:3000


 ⚡ Million Lint v0.0.66
 ✓ Ready in 0.18ms
 ✓ Ready in 2.2s
 ○ Compiling / ...
 ✓ Compiled / in 1158ms (380 modules)
 ✓ Compiled in 180ms (380 modules)
Successfully connected to http://localhost:3000 after 1 attempt(s).
Randomly interacting with page...
Finding element...
Million Lint is working as expected!

Shutting down development server...