Brave Search

1 week ago - An AST-based pattern checker for JavaScript.. Latest version: 10.0.3, last published: 7 days ago. Start using eslint in your project by running `npm i eslint`. There are 24643 other projects in the npm registry using eslint.

      » npm install eslint

Published Mar 06, 2026

Version 10.0.3

Author Nicholas C. Zakas

Repository https://github.com/eslint/eslint

Homepage https://eslint.org

ESLint

eslint.org › docs › latest › use › getting-started

Getting Started with ESLint

You can install and configure ESLint using this command: ... If you want to use a specific shareable config that is hosted on npm, you can use the --config option and specify the package name:

Discussions

Why can't I do npm install after setting up eslint with TypeScript?

You are likely using eslint 9.x version. Use 8.56.x version which should resolve the issue. The latest eslint-ts version is incompatible with eslint 9.x version. You'll need to use the 8.x version for now. More on reddit.com

r/typescript

July 19, 2024

How to run eslint --fix from npm script

I am trying to add lint-fix in my package.json. My basic lint is "lint": "eslint --ext .js,.vue src test/unit/specs test/e2e/specs" I did try "lint-fix": "eslint --fix --ext .js,.vue src test/unit... More on stackoverflow.com

stackoverflow.com

Eslint: How to go about picking an eslint config?

Obviously start with eslint and it's defaults. Then I would include plugins for your specific stack (in this case react + next, maybe typescript)? There are other plugins available like unicorn and sonarjs that I think are really valuable, but that is up to you. For a minimal config, just extend those and see if that works for you. It probably will, but there is plenty to tweak. Don't be afraid to edit rules to match your idea of best practice. Many default rules are arbitrary (e.g. single quotes over double). If you have the time, I actually recommend extending the "all" version of configs, basically enabling every single rule possible. Then go through all the resulting lint errors and either decide if you like the rule (fix your code) or if it's a stupid rule (disable the rule) Once you fix all the errors, you end up with a eslint config that is perfect for you. But it can take like an hour or so to iterate. This is my eslint config that follows that method https://github.com/JacobLey/jacobley/blob/main/root/jacobley/.eslintrc.cjs As for linting those individually, eslint has the ability to selectively turn on/off rules based on file and directory. But ideally you don't need to do much of that, as configs like React simply won't have an effect on your express app. But sometimes things like testing files/directories are allowed to play by different rules than production code, so eslint settings are nice. More on reddit.com

r/node

August 4, 2022

An eslint plugin for NestJs with rules for modules and Open API/swagger decorators

u/darraghor great plugin, however it seem to be detecting GET(':id') as invalid while GET(":id") as valid. Both should work with NestJS. I've patched "paramDecoratorNameMatchesRouteParam.js" in my project with the following and it solved it for myself. const isParameterNameIncludedInAPathPart = (paramName, pathPartsToCheck) => { return pathPartsToCheck.some((pathPart) => { return (pathPart === \":${paramName}"` ||` pathPart === `':${paramName}'` || pathPart.includes(\/:${paramName}/`) ||` pathPart.includes(\/:${paramName}"`) ||` pathPart.includes(\":${paramName}/`));` }); }; More on reddit.com

r/node

January 27, 2021

Videos