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

@hyperfrontend/linter

v0.3.4

Published

A linter for TypeScript, JavaScript, JSX, JSON and Markdown with its own parsers and no external runtime packages.

Readme

A linter for TypeScript, JavaScript, JSX, JSON and Markdown with its own parsers and no external runtime packages.

• 👉 See documentation

• 👉 See guides & tutorials

What is @hyperfrontend/linter?

@hyperfrontend/linter checks TypeScript, JavaScript, JSX, JSON and Markdown against rules you choose, and fixes what the rules know how to fix. It parses every file with parsers of its own and installs no dependencies.

It is not a drop-in ESLint. It reimplements a selection of rules from ESLint and well-known plugins, under a configuration that reads like ESLint's flat config, and it does not load ESLint plugins, parsers or shareable configs.

Key Features

  • Packaged rules - Core JavaScript, TypeScript, JSDoc, React, React hooks and package.json rules, and a set of conventions
  • Presets to start from - The rules the upstream recommended configurations turn on, as plain objects you spread into a block
  • One parse, one traversal - The listeners of every rule in effect for a file run in a single walk of its tree
  • Rules of your own - Register them under a prefix with families and test them with testRule
  • Fixes and suggestions - --fix applies fixes; suggestions, for changes that need your judgement, appear in the JSON report
  • No dependencies - The package is self-contained; linting loads nothing from npm

Architecture Highlights

Every file is parsed once and every rule's listeners run in one traversal of it; the services rules share, such as scopes and code paths, are computed once per file and never rebuilt. The architecture guide covers the parsers, the shared services and the fix loop.

Why Use @hyperfrontend/linter?

Fewer packages in the toolchain

A linting setup built on ESLint brings a parser, plugins and their dependencies into every install. This package is one dependency with nothing beneath it, for a project whose checks fit its rules.

Rules you can read and own

Each rule is one module with its specification beside it. When the packaged rules stop short, write and test a rule of your own with the same API they use.

Installation

npm install --save-dev @hyperfrontend/linter

Requires Node.js 24 or later, which loads the TypeScript configuration file without a compiler.

Quick Start

Create lint.config.ts at the project root:

import { CODE, CODE_RULES, on } from '@hyperfrontend/linter'

export default [
  { ignores: ['dist/', 'coverage/'] },
  { files: CODE, rules: CODE_RULES },
  { files: ['src/**/*.ts'], rules: on('no-enum import-order') },
]

Then lint and fix from the project root:

npx hf-lint
npx hf-lint src --fix

Lint a project with @hyperfrontend/linter covers configuration, directives, exit codes, CI and linting from code with lint.

API Overview

| Entry | What it is | | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | @hyperfrontend/linter | Running, configuration types and presets, defineRule and the rule types | | /helpers | Tokens, scopes, JSON properties and positions, for rules of your own | | /testing | testRule, which turns a rule's cases into node:test tests | | hf-lint | The command line |

Every rule, with its options and examples, is in the rule catalogue. Moving from ESLint? Replace ESLint with @hyperfrontend/linter starts with what does and does not carry over.

Limitations

  • No rule uses type information, and every packaged rule reads only the file it lints.
  • No editor integration: run it from the terminal, a hook or CI.
  • No result cache between runs.
  • YAML files are read as plain lines for rules of your own; no packaged rule reads them.

Acknowledgements

The packaged rules reimplement rules from ESLint, typescript-eslint, eslint-plugin-jsdoc, eslint-plugin-react, eslint-plugin-react-hooks and eslint-plugin-package-json, whose messages, options and test cases they follow; a few of its tables derive from those projects, from globals and from safe-regex. Their licences and the details are in NOTICE.md. How the linter came to be written is told in I Replaced ESLint. The First Attempt Worked. I Threw It Away.

Compatibility

Requires Node.js 24 or later. There is no browser build.

| Operating System | Supported | | ---------------- | :-------: | | Linux | ✅ | | macOS | ✅ | | Windows | ✅ |

Output Formats

| Format | File | Tree-Shakeable | | ------ | ----------------- | :------------: | | ESM | index.mjs | ✅ | | CJS | index.cjs | ❌ | | Bin | bin/hf-lint.mjs | ❌ |

Part of hyperfrontend

This library is part of the hyperfrontend monorepo.

📖 Full documentation

License

MIT