Upgrade standard: 11.0.1 → 13.1.0 (major)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ standard (11.0.1 → 13.1.0) · Repo · Changelog

Release Notes

13.1.0 (from changelog)

• Update eslint from ~6.0.1 to ~6.1.0

13.0.2 (from changelog)

• Fix global installations of standard not finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329

13.0.1 (from changelog)

Changed rules

• Relax rule: Only enforce const in destructuring when all variables are constant #1325

13.0.0 (from changelog)

Welcome to the latest version of standard!

As with every new major release, there are lots of new rules in 13.0.0 designed to help catch bugs and make programmer intent more explicit.

standard is more popular than ever – 640,000 downloads per month! It's even more popular – 3,000,000 downloads per month – if you include the ESLint configuration that we also publish (for advanced users).

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

❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page. GitHub is matching donations, so your dollars go twice as far! 🚀

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.

• The documentation 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 always welcome!

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

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

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 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%)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)