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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@nullvoxpopuli/eslint-configs

v5.3.4

Published

eslint configs for the NullVoxPopuli's projects

Readme

ESLint Configs

npm version

ESLint has grown complicated for projects with variance:

  • JavaScript or TypeScript
  • Node or Browser
  • App or Library
  • Cross-Platform
  • etc

This project aims to simplify both configuring and overriding ESLint configs.

Install

yarn add --dev @nullvoxpopuli/eslint-configs
# or
npm install --save-dev @nullvoxpopuli/eslint-configs
# or 
pnpm add --save-dev @nullvoxpopuli/eslint-configs

And due to how ESLint resolves plugins, you'll need to ensure that all the dependencies of @nullvoxpopuli/eslint-configs are installed in the root node_modules directory.

This is easier with either yarn workspaces or npm. Standalone yarn with non-monorepos nests node_modules which confuses eslint.

Upgrading across major version boundaries

This goes for major bumps of this package, and any plugin within.

You'll want to use eslint-formatter-todo, so that when you encounter new rules, or a plugin changes the defaults, you can mark them as "TODO". This is effectively temporarily turning errors into warnings, but it allows you to incrementally adopt big changes to your lint configs over time.

This is especially useful on large codebases, and when lint rules don't come with auto-fixers.

I'd recommend updating your lint:js script in package.json to:

"scripts": {
  "lint:js": "eslint . --format @lint-todo/eslint-formatter-todo"
}

See the Usage section of eslint-formatter-todo for details.

Usage

Ember

// eslint.config.js  
import { configs } from '@nullvoxpopuli/eslint-configs';

// accommodates: JS, TS, App, Addon, and V2 Addon
export default configs.ember(import.meta.dirname);

overriding

// eslint.config.js  
import { configs } from '@nullvoxpopuli/eslint-configs';

const config = configs.ember(import.meta.dirname);

export default [
    ...config,
    // your modifications here
    // see: https://eslint.org/docs/user-guide/configuring/configuration-files#how-do-overrides-work
];

Cross-Platform

This config is ESM, as ESM is the most widely supported module format across different distributions (browser, node, etc).

// eslint.config.js  
import { configs } from '@nullvoxpopuli/eslint-configs';

export default configs.crossPlatform(import.meta.dirname);

Node

This config looks at your package.json to determine if your project is CommonJS or ES Modules.

// eslint.config.js  
import { configs } from '@nullvoxpopuli/eslint-configs';

export default configs.node(import.meta.dirname);

overriding

// eslint.config.js 
import { configs } from '@nullvoxpopuli/eslint-configs';

const config = configs.node();

export default [
    ...config,
    // your modifications here
    // see: https://eslint.org/docs/user-guide/configuring/configuration-files#how-do-overrides-work
]

Disabling type-aware linting

import { disableTypedLints } from '@nullvoxpopuli/eslint-configs';

export default [
    // ...
    disableTypedLints.forTests,
];