-
-
Notifications
You must be signed in to change notification settings - Fork 2.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
Release proposal: standard v14 #1321
Comments
I really hope that TypeScript will get more treatment since it is still not possible to use standard with it (#1283). Besides, projects which have mixed JavaScript and TypeScript are even in a worse position cause right now we can specify only one parser, while ideally, we'd want to specify different parsers for different files ( |
@ArmorDarks Thanks for the feedback. I posted some thoughts about how to improve Typescript support and other usability issues here: #1356 Your feedback would be appreciated there. As for standard 14, I think these changes might be too much for this release as I want to get this version out the door this week. We'll have to target the typescript stuff for a later version. |
I just released a beta version of standard 14. It's version
The changelog is here: https://github.com/standard/standard/blob/master/CHANGELOG.md#unreleased Announcement tweet: https://twitter.com/StandardJS/status/1161375232596303872 |
I just added a bunch more rules and published a new beta of standard 14. It's version
Again, the changelog is here: https://github.com/standard/standard/blob/master/CHANGELOG.md#unreleased Announcement tweet: https://twitter.com/StandardJS/status/1161836674705494016 |
I just released Cheers! 🍻 |
Thank you for your service to the community, @feross 🙏 🏅 |
@mightyiam Thank you |
I'd like to do another release of major release of
standard
relatively soon afterstandard
13 is released. We have quite a backlog of new rule additions so I'd like to seek feedback from contributors (and the broader community) about what rule or rules should be included in the next release.Please link to an open issue or PR on the
standard
oreslint-config-standard
issue tracker where the rule is discussed. Thanks!The text was updated successfully, but these errors were encountered: