-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
🛠 Repo: Enable ESLint's recommended rules for JS #5281
Comments
Perhaps we could go with https://github.com/neostandard/neostandard as a base? Considering that |
I'm tentatively in favor, but haven't dug into neostandard enough to have a super informed opinion. Is it a superset of ESLint's recommended JS rules, roughly? From what I've seen it seems like it'd be a good next step after this? |
I think we should move to neostandard. |
Following up: since we're already on ESLint, I'm going to go ahead and push #5282 forward. But if someone wants to file an issue around moving to Neostandard I'd be very interested in hearing more. I don't use it myself and haven't kept good track of its latest happenings. |
Thoughts on neostandard @mark-wiemer? |
neostandard is foreign to me but I've skimmed through their readme and whatnot. Biggest concerns are that it's not in v1 and doesn't get super frequent updates nowadays. I do think it's worth exploring more, hence #5301, but I think the "ESLint recommended" ruleset will solve 90% of our problems, so we should merge that for now as an incremental improvement |
I'm the lead maintainer of it 😜 |
Tooling Suggestion Checklist
main
branch of the repository.faq
label, but none matched my issue.Overview
Back in #5060, I'd added an ESLint config but not enabled any of the recommended rules from
js.configs.recommended
. Therules
object is overridden by our custom settings:mocha/eslint.config.js
Lines 11 to 26 in 3c191c0
Additional Info
The fact that I missed this and no reviewers caught it is a testament to the ... joy of being new adopters of flat config. 🙃
The text was updated successfully, but these errors were encountered: