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

@mheob/oxlint-config

v2.2.0

Published

Shared OXLint configuration

Readme

OXLint Config

Opinionated, shared OXLint configuration for my projects.

Install

bun add -D @mheob/oxlint-config oxlint

Usage

Create an oxlint.config.ts at the root of your project and extend one or more of the provided configs:

// oxlint.config.ts
import { baseConfig, baseJsConfig } from '@mheob/oxlint-config';
import { defineConfig } from 'oxlint';

export default defineConfig({
	extends: [baseConfig, baseJsConfig],
});

Combine multiple configs by spreading them into the extends array:

// oxlint.config.ts
import { baseConfig, baseJsConfig, reactConfig, storybookConfig, tailwindcssConfig } from '@mheob/oxlint-config';
import { defineConfig } from 'oxlint';

export default defineConfig({
	extends: [baseConfig, baseJsConfig, reactConfig, storybookConfig, tailwindcssConfig],
});

Add project-specific rule overrides on top:

// oxlint.config.ts
import { baseConfig, baseJsConfig } from '@mheob/oxlint-config';
import { defineConfig } from 'oxlint';

export default defineConfig({
	extends: [baseConfig, baseJsConfig],
	rules: {
		'typescript/no-explicit-any': 'off',
	},
});

Available configs

baseConfig

The foundation for all projects. Enables the following OXLint plugins and covers their most important rules:

| Plugin | Scope | | ------------ | -------------------------------- | | eslint | General JS/TS best practices | | typescript | TypeScript-specific rules | | unicorn | Modern JS idioms and consistency | | import | Import ordering and correctness | | jsdoc | JSDoc comment quality | | node | Node.js safety rules | | oxc | OXC-native rules |

Also ships with file-specific overrides for CLI files, config files, scripts, Markdown code blocks, and Vitest test files (enabling the vitest plugin for spec/test/bench files).

baseJsConfig

Extends baseConfig with additional rules provided via JS plugins. Should be used alongside baseConfig in most projects:

| JS Plugin | Scope | | ---------------------- | ------------------------------------------ | | eslint-plugin-regexp | Regex correctness and optimisation | | eslint-plugin-jsonc | JSON/JSONC/JSON5 key ordering and validity | | eslint-plugin-yml | YAML structural correctness |

Includes file-specific overrides:

  • JSON files (*.json, *.json5, *.jsonc) — key sorting, value validation, and structural rules
  • tsconfig.json — enforces canonical compilerOptions key order
  • YAML files (*.yaml, *.yml) — block mapping, sequence, and whitespace rules

reactConfig

Extends the base with React-specific rules. Applied to **/*.tsx files:

| Plugin / Scope | Description | | --------------- | ----------------------------------------------------------------- | | react | JSX correctness (no duplicate props, no comment text nodes, etc.) | | react-hooks | Rules of hooks enforcement and exhaustive dependency checks | | react-dom | DOM safety (no dangerouslySetInnerHTML, deprecated APIs, etc.) | | react-web-api | Leaked event listeners, intervals, timeouts, and resize observers | | react-perf | Plugin loaded; rules can be enabled per project |

Also turns off typescript/explicit-function-return-type inside .tsx files.

Required peer dependencies:

bun add -D eslint-plugin-react-dom eslint-plugin-react-web-api eslint-plugin-react-x

storybookConfig

Enables Storybook-specific rules for story files (**/*stories.{js,jsx,ts,tsx}) and .storybook/main.ts:

  • Story structure and exports (default-exports, story-exports)
  • Interaction best practices (await-interactions, context-in-play-function)
  • Naming conventions (prefer-pascal-case, no-redundant-story-name)
  • Relaxes no-console, no-alert, and rules-of-hooks inside story files

Required peer dependency:

bun add -D eslint-plugin-storybook

tailwindcssConfig

Enforces consistent Tailwind CSS class usage via eslint-plugin-better-tailwindcss:

| Rule | Severity | | ----------------------------------------------------- | -------- | | better-tailwindcss/enforce-consistent-class-order | warn | | better-tailwindcss/enforce-consistent-line-wrapping | warn | | better-tailwindcss/enforce-canonical-classes | warn | | better-tailwindcss/no-deprecated-classes | warn | | better-tailwindcss/no-duplicate-classes | warn | | better-tailwindcss/no-unnecessary-whitespace | warn | | better-tailwindcss/no-conflicting-classes | error | | better-tailwindcss/no-unknown-classes | error |

Configure the Tailwind CSS entry point and class whitelist in your own oxlint.config.ts:

// oxlint.config.ts
import { baseConfig, baseJsConfig, tailwindcssConfig } from '@mheob/oxlint-config';
import { defineConfig } from 'oxlint';

export default defineConfig({
	extends: [baseConfig, baseJsConfig, tailwindcssConfig],
	settings: {
		tailwindcss: {
			config: './src/styles/index.css',
			whitelist: ['my-prefix-.+'],
		},
	},
});

Required peer dependency:

bun add -D eslint-plugin-better-tailwindcss

Editor integration

VS Code

Install the OXC VS Code extension and add to .vscode/settings.json:

{
	"editor.defaultFormatter": "oxc.oxc-vscode",
	"editor.formatOnSave": true,
	"editor.codeActionsOnSave": {
		"source.fixAll.oxc": "explicit",
	},
}

Zed

Add to .zed/settings.json:

{
	"lsp": {
		"oxc": {
			"initialization_options": {
				"settings": {
					"run": "onSave",
					"configPath": "./oxlint.config.ts",
				},
			},
		},
	},
}

Scripts

Add to your package.json:

{
	"scripts": {
		"format": "oxfmt",
		"format:check": "oxfmt --check",
		"lint": "oxlint",
		"lint:fix": "oxlint --fix"
	}
}