New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add maxWarnings as a configuration option #16804
Comments
We can consider this again, but keep in mind that allowing |
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint (Open eslint issue eslint/eslint#16804)
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint (Open eslint issue eslint/eslint#16804)
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint (Open eslint issue eslint/eslint#16804) [ ] string replace loader does not work [ ] css from Patternfly is not being extracted
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint (Open eslint issue eslint/eslint#16804) [ ] string replace loader does not work [ ] css from Patternfly is not being extracted [1] [1] evanw/esbuild#2905
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint [0] [ ] string replace loader does not work [ ] css from Patternfly is not being extracted [1] [0] eslint/eslint#16804 [1] evanw/esbuild#2905
TODO: [ ] cockpit-po-plugin [ ] fail on warnings eslint [0] [ ] string replace loader needs to replace fake pths [x] css from Patternfly is not being extracted [1] [0] eslint/eslint#16804 [1] evanw/esbuild#2905
For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] cockpit-po-plugin [ ] cockpit-rsync-plugin [ ] stylelint intergration [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] Bundle sizes are much bigger for eslint as files are not compressed [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] Bundle sizes are much bigger for esbuild as files are not compressed, consider if this is needed [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] Bundle sizes are much bigger for esbuild as files are not compressed, consider if this is needed [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] Bundle sizes are much bigger for esbuild as files are not compressed, consider if this is needed [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: [ ] Bundle sizes are much bigger for esbuild as files are not compressed, consider if this is needed [ ] fail on warnings eslint [0] [0] eslint/eslint#16804
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: - [ ] Bundle sizes are much bigger: evanw/esbuild#2933 - [ ] fail on eslint warnings eslint: eslint/eslint#16804 - [ ] sass plugin pulls in older/duplicate esbuild compiler: glromeo/esbuild-sass-plugin#122
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: - [ ] Bundle sizes are much bigger: evanw/esbuild#2933 - [ ] fail on eslint warnings eslint: eslint/eslint#16804 - [ ] sass plugin pulls in older/duplicate esbuild compiler: glromeo/esbuild-sass-plugin#122
Esbuild performance: $ time npm run build > build > node build.js real 0m7.747s user 0m12.328s sys 0m0.508s Webpack performance: [kkoukiou@sequioa cockpit-podman]$ time npm run build > build > webpack Webpack compiled successfully real 0m26.832s user 0m47.778s sys 0m1.640s For eslint integration there are two existing plugins [1], [2] but none can be used because of unsatisfied peer dependency version of esbuild. Let's just use our own eslint plugin for now. [1] to-codando/esbuild-plugin-linter#1 [2] robinloeffel/esbuild-plugin-eslint#5 TODO: - [ ] Bundle sizes are much bigger: evanw/esbuild#2933 - [ ] fail on eslint warnings eslint: eslint/eslint#16804 - [ ] sass plugin pulls in older/duplicate esbuild compiler: glromeo/esbuild-sass-plugin#122
Properly report errors. Unfortunately errors cause eslint watch mode to abort the watch loop, so add a hack to reduce them to warnings in watch mode. Warnings don't fail a normal "npm run build" [1], so we have to make this dynamic for now. [1] eslint/eslint#16804
Properly report errors. Unfortunately errors cause eslint watch mode to abort the watch loop, so add a hack to reduce them to warnings in watch mode. Warnings don't fail a normal "npm run build" [1], so we have to make this dynamic for now. [1] eslint/eslint#16804
Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update. |
@eslint/eslint-team folks your feedback here would be appreciated.
@lourd are you interested in implementing this if approved by the team? The core team is currently focused on implementing a new config system. You can track it's progress here #13481 and rfc. |
I'm not sure if |
@mdjermanovic yeah, that's my feeling as well. I don't believe it belongs in the config file, so closing. |
Those points all make sense. Thank you for the thoughtful consideration! |
ESLint version
8.32.0
What problem do you want to solve?
Resurrecting #13391:
I want to make having a max warnings config value of 0 opt-out instead of opt-in.
My team has a monorepo managed with Nx. It's setup where we share most configuration for each target (library or application) in a root .eslintrc.json, which each target then extends in its own .eslintrc.json file.
One key configuration that can't be shared is the max warnings. When making a new library or application, the developer has to remember to add that to the additional configuration file (in Nx's case, the configuration for the eslint executor in the
project.json
).This often gets forgotten, causing linter warnings build up and making it difficult to get back into good shape.
What do you think is the correct solution?
I'd like eslint to have the ability to set maxWarnings as a property in a .eslintrc.json file, not just through the command line.
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: