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

@utoo/lint

v0.1.3

Published

Experimental JavaScript and TypeScript linter powered by Yuku

Downloads

1,590

Readme

@utoo/lint

utoo-lint logo

High performance linter for JavaScript and TypeScript written by Zig.

Install

pnpm add -D @utoo/lint

CLI

Run the linter with:

pnpm exec utoo-lint src

If no target is provided, utoo-lint uses files from utoo.json or utoo-lint.json. When no config file or files entry exists, it scans the current directory. It skips .git, .zig-cache, node_modules, vendor, and zig-out.

Use a config file:

pnpm exec utoo-lint --config=utoo.json src

Run a focused rule set:

pnpm exec utoo-lint --rules=no-debugger,no-console src

Use machine-readable output:

pnpm exec utoo-lint --format=json src

Configuration

Create a utoo.json file:

{
  "$schema": "https://raw.githubusercontent.com/fireairforce/utoo-lint/main/npm/utoo-lint/schema.json",
  "files": ["src/**/*.{js,jsx,ts,tsx}"],
  "ignores": ["dist", "node_modules"],
  "rules": {
    "no-console": "off",
    "no-debugger": "error"
  }
}

Start from the packaged frontend template:

cp node_modules/@utoo/lint/configs/frontend.json utoo.json

ESLint Migration

Convert an existing ESLint config into the native utoo format:

pnpm exec utoo-lint migrate eslint --from eslint.config.js --output utoo.json

The package also provides compatibility bins for common replacement flows:

pnpm exec eslint --config utoo.json src
pnpm exec fishlint eslint --disable-setup --config utoo.json --glob src

JavaScript API

import { lintFiles } from "@utoo/lint";

const report = lintFiles(["src"], {
  config: "utoo.json",
  rules: ["no-debugger"]
});

console.log(report.diagnostics);

Calling lintFiles() without patterns follows the same default target behavior as the CLI, so migration scripts usually do not need to expand config files manually.

CommonJS is supported through require("@utoo/lint").

Binary Resolution

@utoo/lint installs a platform-specific optional dependency containing the native utoo-lint binary. Set UTOO_LINT_BIN=/path/to/utoo-lint to force a specific binary during local development.