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 v9 #780
Comments
Sorry for all the notification spam today. I've been busy merging a lot of new rules for v9. 🛠 💻 So, a bit of background... I was planning to put a lot more rules into this release, but as I went along adding rules and testing the ecosystem impact, it got to a point where I realized we're already affecting a decent number of users. Large releases make it hard for users to upgrade, so it's best to only include 1-2 big breaking rules per release. This release has 3. So I think we should just call what we have so far v9 and release it before the end of the month. Then we can release v10 shortly thereafter, with the rest of these rules. Something like this: 2/8 (today) - v9 (beta) |
Sounds good to me |
I'm happy to announce the immediate availability of a You try it out today by installing it: Cheers! 🎉 |
Why put the beta version on the npm I'm asking because I use a dependency update checker that can automatically patch package.json files for me to packages' latest versions, but I'm hesitant to install the "beta" version of the linter, forcing me to manually revert the package.json entry... |
@SEAPUNK I did this intentionally to get more eyeballs on the new version, but I didn't realize it would false-alarm automated tools. Added a dist-tag. |
Thank you! |
Change log: https://github.com/feross/standard/blob/master/CHANGELOG.md#900---2017-02-28 |
Planned release date: Mar 1, 2017. (approx. 22 days from the date of this issue)
Try it now:
npm install standard@beta --global
New features
standard --fix
!New rules
(Estimated % of affected standard users, based on test suite in parens)
typeof
expressions against string literals (valid-typeof) #629 (0%)Changed rules
The text was updated successfully, but these errors were encountered: