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

@ver0/eslint-config

v1.7.1

Published

ESLint configs used in all ver0 projects

Readme

NPM Version NPM Downloads Dependents (via libraries.io), scoped npm package GitHub Actions Workflow Status

✨ What's Included

A collection of modular ESLint configs — import only what you need and compose them with defineConfig().

  • JavaScript — base rules, import sorting, unicorn, promise, ESLint comments
  • TypeScript — type-aware linting via XO TypeScript config
  • React — JSX, hooks, and import rules
  • Node.js — Node globals and eslint-plugin-n rules
  • Browser — browser globals and restricted globals
  • JSON.json, .jsonc, .json5 linting
  • Markdown — Markdown linting
  • Svelte — Svelte component and runes module linting
  • Vitest — test file rules
  • Prettier — formatting integration

🚀 Installation

yarn add -D @ver0/eslint-config eslint

Each config requires its own peer dependencies — see Available Configs below.

📖 Usage

Import the configs you need and compose them with defineConfig():

// eslint.config.js
import {defineConfig} from 'eslint/config';
import javascript from '@ver0/eslint-config/javascript.js';
import node from '@ver0/eslint-config/node.js';
import json from '@ver0/eslint-config/json.js';
import markdown from '@ver0/eslint-config/markdown.js';
import prettier from '@ver0/eslint-config/prettier.js';

export default defineConfig(javascript, node, ...json, markdown, prettier);

Note: The JSON config exports an array of 3 configs (JSON, JSONC, JSON5), so spread it with ...json.

📦 Available Configs

Each config is a standalone module. Import it to enable, skip it to disable — no options object needed. If the required peer dependencies are not installed, you'll get a clear error listing exactly what's missing.

  • JavaScript — base rules, import sorting, unicorn, promise, ESLint comments. Always include this one — other configs build on top of it.

    yarn add -D @eslint/js @eslint-community/eslint-plugin-eslint-comments eslint-plugin-import eslint-plugin-promise eslint-plugin-unicorn eslint-plugin-no-use-extend-native eslint-config-xo
  • TypeScript — type-aware linting rules. Also exports typescriptUnsafe to disable strict type-safety rules.

    yarn add -D eslint-config-xo-typescript typescript
  • React — React, JSX, and hooks rules.

    yarn add -D eslint-plugin-import eslint-config-xo-react
  • Node.js — Node.js globals and eslint-plugin-n rules.

    yarn add -D globals eslint-plugin-n
  • Browser — browser globals and restricted globals (prevents accidental use of confusing browser globals like event, name, etc.).

    yarn add -D globals confusing-browser-globals
  • JSON — linting for .json, .jsonc, and .json5 files. Exports an array of 3 configs — spread it with ...json in defineConfig().

    yarn add -D @eslint/json
  • Markdown — Markdown linting.

    yarn add -D @eslint/markdown
  • Svelte — Svelte component and runes module linting via eslint-plugin-svelte. Exports an array of configs — spread it with ...svelte in defineConfig().

    yarn add -D eslint-plugin-svelte
  • Vitest — rules for test and benchmark files (*.test.*, *.benchmark.*).

    yarn add -D @vitest/eslint-plugin
  • Prettier — formatting integration. Include this last so it overrides conflicting rules.

    yarn add -D eslint-plugin-prettier eslint-config-prettier prettier

🌟 Common Configurations

Node.js API project:

// eslint.config.js
import {defineConfig} from 'eslint/config';
import javascript from '@ver0/eslint-config/javascript.js';
import typescript from '@ver0/eslint-config/typescript.js';
import node from '@ver0/eslint-config/node.js';
import json from '@ver0/eslint-config/json.js';
import markdown from '@ver0/eslint-config/markdown.js';
import vitest from '@ver0/eslint-config/vitest.js';
import prettier from '@ver0/eslint-config/prettier.js';

export default defineConfig(javascript, typescript, node, ...json, markdown, vitest, prettier);

React web application:

// eslint.config.js
import {defineConfig} from 'eslint/config';
import javascript from '@ver0/eslint-config/javascript.js';
import typescript from '@ver0/eslint-config/typescript.js';
import react from '@ver0/eslint-config/react.js';
import browser from '@ver0/eslint-config/browser.js';
import json from '@ver0/eslint-config/json.js';
import vitest from '@ver0/eslint-config/vitest.js';
import prettier from '@ver0/eslint-config/prettier.js';

export default defineConfig(javascript, typescript, react, browser, ...json, vitest, prettier);

SvelteKit application:

// eslint.config.js
import {defineConfig} from 'eslint/config';
import javascript from '@ver0/eslint-config/javascript.js';
import typescript from '@ver0/eslint-config/typescript.js';
import svelte from '@ver0/eslint-config/svelte.js';
import browser from '@ver0/eslint-config/browser.js';
import json from '@ver0/eslint-config/json.js';
import vitest from '@ver0/eslint-config/vitest.js';
import prettier from '@ver0/eslint-config/prettier.js';

export default defineConfig(javascript, typescript, ...svelte, browser, ...json, vitest, prettier);

🎨 Prettier Configuration

This package also provides an opinionated default Prettier configuration that you can extend from.

// .prettierrc.js
import ver0Config from '@ver0/eslint-config/.prettierrc.js';

export default {
	...ver0Config,
	// Override any settings if needed
	// printWidth: 100,
};

⚙️ EditorConfig

For consistent formatting across different editors, you can copy our .editorconfig that is aligned with our Prettier configuration:

# .editorconfig
[*]
indent_style = tab
tab_width = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
max_line_length = 120

[*.yml]
indent_style = space
indent_size = 2

🛠️ Troubleshooting

Rules conflicting with your existing setup? You can override specific rules by adding a config after ours:

// eslint.config.js
import {defineConfig} from 'eslint/config';
import javascript from '@ver0/eslint-config/javascript.js';
import node from '@ver0/eslint-config/node.js';
import prettier from '@ver0/eslint-config/prettier.js';

export default defineConfig(javascript, node, prettier, {
	rules: {
		'some-rule': 'off', // Override any rule
	},
});