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

@bust/eslint-config

v2.0.0

Published

Shared ESLint configuration for Busticated JS/TS projects

Readme

@bust/eslint-config

Shared ESLint configuration for Busticated JS/TS projects

Installation

npm install @bust/eslint-config --save-dev

eslint is a peer dependency - everything else this config needs (typescript-eslint, @stylistic, the React and Vitest plugins) ships with it, so there is nothing else to install.

Usage

Call the factory from your eslint.config.js and export the result. It targets TypeScript by default, with type-aware rules on.

// eslint.config.js
import bust from '@bust/eslint-config';

export default bust();

Options turn on the layers a project needs:

export default bust({
	react: true,
	vitest: true,
	ignores: ['.output/', '.nitro/'],
});

JavaScript-only projects

typescript: false drops typescript-eslint and the type-aware rules, keeping the same core and stylistic rules with the built-in no-unused-vars and no-use-before-define in place of their TS-aware equivalents.

export default bust({ typescript: false });

Test runners

vitest: true adds Vitest's recommended rules. nodeTest: true is for projects on node:test, where describe() and it() return promises nobody awaits - it relaxes no-floating-promises across the spec, test, e2e, and integration suites, and does nothing when the type-aware rules are off.

Type-aware rules

These are on by default and need your tsconfig.json to cover every file being linted. A file the tsconfig lists but excludes - an eslint.config.js in a project without allowJs, say - needs naming explicitly:

export default bust({ allowDefaultProject: ['eslint.config.js'] });

Turn them off with typeAware: false if a project's tsconfig isn't ready for it.

Overriding

The factory returns a flat-config array, so append your own blocks - later blocks win:

export default [
	...bust(),
	{
		files: ['bin/**'],
		rules: { 'no-console': 'off' },
	},
];

Every block this package contributes is named bust/*, so npx eslint --inspect-config will tell you which one applied a given rule.

API

see here

NOTE: When in doubt, check usage in tests

License

See LICENSE.md