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
Release proposal: 15.0.0 #1560
Comments
I have revised my list and want to do a bit less controversial release. standard/eslint-config-standard#166 & standard/eslint-config-standard#152 breaks compatibility with older browsers, and it seems like not everyone is ready for that just yet. standard/eslint-config-standard#148 seems like it could bring with a number of false positives, which generally have been something that we really want to avoid, so that Standard "gets out of your way" as it were. standard/eslint-config-standard#94 has some eco system breakage that we should investigate and potentially tweak the rule before merging it, or dropping the rule... With that said I want to cut a 15 release that mainly focuses on the upgrade to ESLint 7, and adding compatibility with modern code that uses ES2020 features. Unless no-one objects in a few days, I shall cut a release with just the PRs in the first group 🎉 |
How about #1431? |
Rolling out eslint 7 as a single upgrade is a good idea. I’d be happy to help with that. |
Could you also enable |
I'm working on this today. |
How about #1559 ? Can you check if it can be done? |
I'm going to save the rules which have huge amounts of breaking changes for a future version. |
standard 15.0.0 is released! This release took me 6 hours of work to put together. Announcement tweet: https://twitter.com/StandardJS/status/1319109569675554816 Hope you enjoy it! |
We'll have to do a major version to get ESLint 7.x support, and I wanted to see if there is anything else we want to merge in as well. My preliminary list:
Breaks old runtime compat:
High eco system breakage:
The text was updated successfully, but these errors were encountered: