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
Upgrade to ESLint 7.x #1518
Comments
All of these changes are reasonable. I'm excited about bumping to eslint @ 7. |
Is there anything specifically blocking progress on this? The reason I ask is. ESLint isn't equipped to backport security fixes to the prior SemVer Major and another vulnerability was found in Lodash (ie which ESLint uses). It'll probably be an easy fix (ie bump sub deps) but sometimes it isn't (ie the offending sub dep isn't maintained). Keeping StandardJS in lockstep with ESLint's SemVer major can help this by ensuring any recent patches to ESLint are immediately available. Sorry in advance if this is annoying. I woleheartedly agree. |
When upgrading to 7.x, if you jump to 7.4 directly, could you consider adding this option? #1474 I contributed the feature myself to eslint so that it could be included in standard, if you agree 😉 |
In #1539 (referenced by @shadowspawn) I asked for ESLint 7.5 because of the Optional Chaining operator (and the Nullish Coalescing operator by extension). |
Hey, guys, please... This issue must move on... |
I'm working on this today. |
This will be released in standard v15. |
We should also consider adding these new rules:
ref: https://eslint.org/blog/2020/05/eslint-v7.0.0-released
The text was updated successfully, but these errors were encountered: