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

@fc3/eslint-plugin

v0.1.1

Published

Custom ESLint rules and the shared lint configuration for @fc3 projects

Readme

@fc3/eslint-plugin

Custom ESLint rules and the shared lint configuration for @fc3 projects.

Usage

Install the plugin alongside ESLint:

npm install --save-dev eslint @fc3/eslint-plugin

Then make it your eslint.config.mjs:

import FC3 from '@fc3/eslint-plugin';

export default FC3.configs.recommended;

The recommended config bundles @eslint/js recommended, typescript-eslint recommended, eslint-config-prettier, the shared naming and unused-variable rules used across @fc3 projects, and every rule in this plugin. To use only the rules, register the plugin yourself:

import FC3 from '@fc3/eslint-plugin';

export default [
	{
		plugins: {'@fc3': FC3},
		rules: {'@fc3/import-order': 'error'}
	}
];

Rules

@fc3/import-order

Imports at the top of a file must be grouped, in this order:

  1. Node core modules (fs, path, node:http)
  2. Third-party modules (eslint, formidable)
  3. First-party modules (anything under @fc3)
  4. Local modules, resolved against src/ from the project root

Each group is separated from the next by exactly one blank line. Within a group, imports are sorted by the length of their specifiers, so that the imported names form an ascending staircase. Local imports must use the project's baseUrl style absolute path rather than a relative one.

The rule is auto-fixable: eslint --fix rewrites the whole import block into the expected order.

Development

npm install
./bin/test
./bin/lint