
Security News
Open Source Maintainers Feeling the Weight of the EU’s Cyber Resilience Act
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.
@nullvoxpopuli/eslint-configs
Advanced tools
ESLint has grown complicated for projects with variance:
This project aims to simplify both configuring and overriding ESLint configs.
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.
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.
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
]
import { disableTypedLints } from '@nullvoxpopuli/eslint-configs';
export default [
// ...
disableTypedLints.forTests,
];
FAQs
eslint configs for the NullVoxPopuli's projects
We found that @nullvoxpopuli/eslint-configs demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The EU Cyber Resilience Act is prompting compliance requests that open source maintainers may not be obligated or equipped to handle.
Security News
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
Research
/Security News
Undocumented protestware found in 28 npm packages disrupts UI for Russian-language users visiting Russian and Belarusian domains.