Release proposal: standard v9

[feross]

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

• Update ESLint from 3.10.x to 3.15.x.
• 3 additional rules are now fixable with standard --fix!

New rules

(Estimated % of affected standard users, based on test suite in parens)

• Disallow mixing different operators without parens (no-mixed-operators) #566 (5%)
• Enforce 1 newline at end of file (previously 1 or 2 were ok) (no-multiple-empty-lines) #733 (3%)
• Disallow Unused Expressions (no-unused-expressions) #690 (3%)
  • Note: this affects users of the Chai test framework. Read about the changes you need to make.
• Disallow redundant return statements (no-useless-return) #694 (1%)
• Disallow Incorrect Early Use (no-use-before-define) #636 (0%)
• Enforce that Promise rejections are passed an Error object as a reason (prefer-promise-reject-errors) #777 (0%)
• Enforce comparing typeof expressions against string literals (valid-typeof) #629 (0%)
• Enforce spacing around * in generator functions (generator-star-spacing) #724 (0%)
• Disallow Unnecessary Labels (no-extra-label) #736 (0%)
• Disallow spacing between template tags and their literals (template-tag-spacing) #755 (0%)
• Disallow padding within switch statements and classes (padded-blocks) #610 (0%)
• Enforce that Symbols are passed a description (symbol-description) #630 (0%)

Changed rules

• Relax rule: allow TypeScript Triple-Slash Directives (spaced-comment) #660
• Relax rule: allow Flow Comments (spaced-comment) #661

[feross]

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)
3/1 - v9
4/1 - v10 beta
5/1 - v10

[dcousens]

Sounds good to me

[feross]

I'm happy to announce the immediate availability of a standard v9 release candidate. The version is 9.0.0-beta.0.

You try it out today by installing it: npm install standard@beta --global

Cheers! 🎉

[SEAPUNK]

Why put the beta version on the npm latest tag, if it's unreleased?

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...

[feross]

@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.

[SEAPUNK]

Thank you!

[feross]

standard 9.0.0 is released, one day ahead of schedule! 🎉

Change log: https://github.com/feross/standard/blob/master/CHANGELOG.md#900---2017-02-28
Tweet: https://twitter.com/feross/status/836710564130803714