Release proposal: standard v13

[feross]

Planned release date: July 8

Please give feedback! Run npx standard@next or npm install standard@next to try it out.

When you upgrade, consider running standard --fix to automatically format your code to match the newly added rules.

New features

• Update eslint from ~5.16.0 to ~6.0.1

  • BREAKING: Node.js 6 is no longer supported
    • Node.js 6 is EOL and will no longer be receiving security updates. As a result, the eslint team has decided to drop support for it.
    • To prevent breaking CI for projects which still support Node 6, standard silently passes when run by an unsupported version of Node.
  • For eslint-config-standard users only: Plugins are no longer affected by eslint's location
    • Previously, ESLint loaded plugins relative to the location of the ESLint package itself. As a result, we suggested that users with global ESLint installations should also install plugins globally, and users with local ESLint installations should install plugins locally.
    • With ESLint v6, plugins should always be installed locally, even if ESLint was installed globally. More precisely, ESLint v6 resolves plugins relative to the end user’s project by default, and always resolves shareable configs and parsers relative to the location of the config file that imports them.
    • See migrating to ESLint 6.0.0 for more information.

• Update eslint-plugin-promise from ~4.0.0 to ~4.2.1

  • No significant changes

• Update eslint-plugin-node from ~7.0.1 to ~9.1.0

  • No significant changes

• The README is now available in Japanese 🇯🇵!

  • Thanks to @Munieru for the excellent work!
  • Other community contributed translations exist in Spanish, French, Italian, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin. More translations are welcome.

New rules

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

• Disallow spaces inside of array brackets (array-bracket-spacing) #1203 eslint-config-standard/#131 (14%)
• Require const instead of let if variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 (14%)
• Disallow quotes around object literal property names that are not strictly required (quote-props) #791 (4%)
• Disallow use of Object.prototypes builtins directly (no-prototype-builtins) #1310 (3%)
• Require an empty line between class members (lines-between-class-members) #438 (1%)
• Disallow using an async function as a Promise executor (no-async-promise-executor) #1309 (1%)
• Disallow assignments that can lead to race conditions due to usage of await or yield (require-atomic-updates) #1314 (1%)
• Disallow spaces inside of computed properties (computed-property-spacing) #1315 eslint-config-standard/#131 (1%)
• Disallow unnecessary catch clauses (no-useless-catch) #1312 (0%)
• Disallow characters which are made with multiple code points in character class syntax (no-misleading-character-class) #1311 (0%)

[mightyiam]

Lovely to see progress! Thank you for your service to the community, @feross! 💓

[feross]

You're welcome, @mightyiam. ✨

[voxpelli]

Lovely with a new release! Would it be possible to still get https://github.com/standard/eslint-config-standard/issues/129 in there?

[voxpelli]

This one would also be neat: standard/eslint-config-standard#136

[feross]

(I removed the #1314 rule because of false positive reports.)

standard 13.0.0 is released now!

[fanatid]

@feross thank you for release! @Flet can you release new version of semistandard?

[jprichardson]

Thanks @feross!

@Flet if you are able to release a new https://github.com/Flet/semistandard we'd be grateful. We could then get all devDeps in indutny/bn.js#220 in one clean and tidy PR 😜

[feross]

@Flet Lmk if you want me to publish the new semistandard. I don't think I have publish permission on the various packages, e.g. eslint-config-semistandard, so I can't do it.

Related, I think we should make an org so it is easier to manage npm permissions: #1324

[Flet]

Yeah @feross, time to move it to the standard org I think :)

[feross]

@Flet Sure, if you want to transfer the semistandard repo here, it might be easier to keep an eye on it. Up to you :)

I do think that an npm org would make it easier to manage the npm permissions at least.

[fanatid]

@feross can you show how I can measure ecosystem impact for new rules? (like you done for new rules here)
Would like to check arrow-parens for always.

[feross]

can you show how I can measure ecosystem impact for new rules?

You run the test suite and then take the number of failing tests divided by the total number of tests.