Update dependency standard to v13

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
standard (source)	devDependencies	major	6.0.8 -> 13.0.2

---

Release Notes

standard/standard

v13.0.2

Compare Source

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

v13.0.1

Compare Source

Changed rules

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

v13.0.0

Compare Source

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

v12.0.1

Compare Source

• Since ESLint 5 no longer supports Node 4, standard silently passes when run in Node 4, which matches the current behavior for Node 0.10, 0.12, and all other unsupported versions of Node.

v12.0.0

Compare Source

New version of ESLint, new version of Standard!

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

New features

• Update eslint from ~4.19.0 to ~5.4.0.
  • Support JSXFragment nodes (e.g. <></>)
  • Lots of minor changes to rules to catch more edge cases!
• The README is now available in French! (Thanks @​charliegerard!)
  • Other community contributed translations exist in Spanish, 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)

• Require spacing inside of braces (object-curly-spacing) #​609 eslint-config-standard/#​35 (29%)
• Disallow APIs that were deprecated in Node 10 (no-deprecated-api) #​1164 (15%)
  • e.g. assert.equal(), assert.deepEqual() and assert.notEqual() were deprecated in Node 10.
• Disallow self assignment of properties (no-self-assign) #​1186 (0%)

Changed rules

None.

v11.0.1

Compare Source

v11.0.0

Compare Source

This release has no new rules, but it does update to the latest version of eslint,
version 4, which has some significant changes to existing rules. Most updates make
the indentation rules more strict.

Thankfully, most users will just need to run standard --fix to update code to be
compliant.

New features

• Update eslint from ~3.19.0 to ~4.18.0.

  • The indent rule is more strict.
  • The padded-blocks rule is more strict.
  • The space-before-function-paren rule is more strict.
  • The no-multi-spaces rule is more strict.
  • Minor improvements to:
  • no-extra-parens,
  • no-unexpected-multiline,
  • no-regex-spaces, and
  • space-unary-ops

• Update eslint-plugin-import from ~2.2.0 to ~2.8.0

  • Updated for eslint 4.0 compatibility.
  • Various small bug fixes included related to import/* rules.

• Update eslint-plugin-node from ~4.2.2 to ~6.0.0

  • The no-deprecated-api rule is updated with Node.js 8 support and improved
    Node 6 support.

• Upodate eslint-plugin-promise from ~3.5.0 to ~3.6.0.

• Update eslint-plugin-react from ~6.10.0 to ~7.6.1

  • Fix jsx-indent crash
  • Fix jsx-indent indentation calculation with nested JSX.
  • Fix jsx-no-undef will not check the global scope by default.
  • Fix jsx-curly-spacing newline with object literals bug.
  • Fix jsx-curly-spacing schema incompatibility with ESLint 4.2.0.
  • Fix alignment bug in jsx-indent.

Changed rules

• Relax rule: Don't mark Rails Asset Pipeline comments (comments that start with //=)
  as errors. (spaced-comment) #​918

👏 Huge thanks to @​Flet for putting together most of this
release!

v10.0.3

Compare Source

• Internal changes (incremented dependency versions)

v10.0.2

Compare Source

Changed rules

• Relax rule: Disallow import of modules using absolute paths (import/no-absolute-path) #​861
  • This rule was responsible for up to 25% of the running time of standard, so we are disabling it until its performance improves.

v10.0.1

Compare Source

• Internal changes (incremented dependency versions)

v10.0.0

Compare Source

standard just turned 10.0.0! 🎉

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

standard is more popular than ever – 330,000 downloads per month! It's even
more popular – 670,000 downloads per month – if you include the
shareable ESLint config
that we also publish.

The most important change in 10.0.0 is that using deprecated Node.js APIs is now
considered an error. It's finally time to update those dusty old APIs!

Deprecated APIs are problematic because they may print warning messages in the
console in recent versions of Node.js. This often confuses users and leads to
unnecessary support tickets for project maintainers.

Some deprecated APIs are even insecure (or at least prone to incorrect usage) which
can have serious security implications. For that reason, standard now considers
usage of Buffer(num) to be an error, since this function returns uninitialized
program memory which could contain confidential information like passwords or keys.

Instead of Buffer(num), consider using Buffer.alloc(num) or Buffer.from(obj)
which make the programmer's intent clearer. These functions exist in all currently
supported versions of Node.js, including Node.js 4.x. For more background,
see this Node.js issue.

We also improved some rules to support common patterns in code bases that use
React, JSX, and Flow.

When you upgrade, consider running standard --fix to automatically fix some of
the issues caught by this new version.

New features

• Update ESLint from 3.15.x to 3.19.x.
• Node.js API: Add standard.lintTextSync method

New rules

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

• Disallow using deprecated Node.js APIs (node/no-deprecated-api) #​693 (13%)
  • Ensures that code always runs without warnings on the latest versions of Node.js
  • Ensures that safe Buffer methods (Buffer.from(), Buffer.alloc()) are used instead of Buffer()
• Enforce callbacks always called with Node.js-style error first (standard/no-callback-literal) #​623 (3%)
  • Functions named callback or cb must be invoked with null, undefined, or an Error as the first argument
  • Disallows using a string instead of an Error object
  • Disallows confusing callbacks that do not follow the standard Node.js pattern
• Disallow any imports that come after non-import statements (import/first) #​806 (1%)
• Disallow unnecessary return await (no-return-await) #​695 (0%)
• Disallow comma-dangle in functions (comma-dangle) #​787 (0%)
• Disallow repeated exports of names or defaults (import/export) #​806 (0%)
• Disallow import of modules using absolute paths (import/no-absolute-path) #​806 (0%)
• Disallow Webpack loader syntax in imports (import/no-webpack-loader-syntax) #​806 (0%)
• Disallow comparing against -0 (no-compare-neg-zero) #​812 (0%)

Changed rules

• Relax rule: allow using ...rest to omit properties from an object (no-unused-vars) #​800
  • This is a common and useful pattern in React/JSX apps!
• Relax rule: allow Flow import type statements (import/no-duplicates) #​599
  • These are no longer considered to be "duplicate imports"
• Relax rule: Treat process.exit() the same as throw in code path analysis (node/process-exit-as-throw) #​699
  • Makes certain other rules work better and give fewer false positives
• Relax rule: allow Unnecessary Labels (no-extra-label)
  • Redundant, since "no-labels" is already enabled, which is more restrictive

v9.0.2

Compare Source

Changed rules

• Relax rule: Allow tagged template string expressions (no-unused-expressions) #​822

v9.0.1

Compare Source

Changed rules

• Relax rule: Allow mixing basic operators without parens (no-mixed-operators) #​816
  • Specifically, these operators: +, -, *, /, %, and **

v9.0.0

Compare Source

It's time for a new major version of standard! As usual, this release contains a
bunch of awesomeness to help you keep your code in tip-top shape!

We've added several new rules designed to catch potential programmer errors
(i.e. bugs), as well as rules to make programmer intent more explicit in
certain circumstances.

This release continues our trend of tightening up rules so that, wherever possible,
there's one "right" way to do things. This design goal is intended to reduce the
time that teams and maintainers spend giving code review feedback in pull requests.

When you upgrade, consider running standard --fix to automatically fix some of the
errors caught by the new rules in this version.

Note: If you use the Chai test framework, you will need to make some changes to
your tests to improve their robustness. Read about the changes you need to make.

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

v8.6.0

Compare Source

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

v8.5.0

Compare Source

• Update ESLint from 3.7.x to 3.8.x
• 2 additional rules are now fixable with standard --fix

v8.4.0

Compare Source

• Update ESLint from 3.6.x to 3.7.x
• 5 additional rules are now fixable with standard --fix
• Use more conservative semver ranges #​654

v8.3.0

Compare Source

The last release (8.2.0) added ES7 support. This release (8.3.0) adds ES8
support ...just 3 days later!

This release should eliminate the need to specify babel-eslint as a custom
parser, since standard can now parse ES8 (i.e. ES2017) syntax out of the box.
That means async and await will just work.

• Support ES8 (i.e. ES2017) syntax.

v8.2.0

Compare Source

For many users, this release should eliminate the need to specify babel-eslint as
a custom parser, since standard can now parse ES7 (i.e. ES2016) syntax out of the
box.

• Support ES7 (i.e. ES2016) syntax.
• Update ESLint from 3.5.x to 3.6.x
• 4 additional rules are now fixable with standard --fix

v8.1.0

Compare Source

• Update ESLint from 3.3.x to 3.5.x
• Around 10 additional rules are now fixable with standard --fix

v8.0.0

Compare Source

This release contains a bunch of goodies, including new rules that catch potential
programmer errors (i.e. bugs) and enforce additional code consistency.

However, the best feature is surely the new --fix command line flag to
automatically fix problems. If you ever used
standard-format
and ran into issues with the lack of ES2015+ support, you'll be happy about
--fix.

standard --fix is built into standard v8.0.0 for maximum convenience, it
supports ES2015, and it's lightweight (no additional dependencies since it's part
of ESLint which powers standard). Lots of problems are already fixable, and more
are getting added with each ESLint release.

standard also outputs a message ("Run standard --fix to automatically fix
some problems.") when it detects problems that can be fixed automatically so you
can save time!

With standard v8.0.0, we are also dropping support for Node.js versions prior to
v4. Node.js 0.10 and 0.12 are in maintenance mode and will be unsupported at the
end of 2016. Node.js 4 is the current LTS version. If you are using an older
version of Node.js, we recommend upgrading to at least Node.js 4 as soon as
possible. If you are unable to upgrade to Node.js 4 or higher, then we recommend
continuing to use standard v7.x until you are ready to upgrade Node.js.

Important: We will not be updating the standard v7.x versions going forward.
All bug fixes and enhancements will land in standard v8.x.

Full changelog below. Cheers!

New features

• Upgrade to ESLint v3 (http://eslint.org/docs/user-guide/migrating-to-3.0.0) #​565
  • BREAKING: Drop support for node < 4 (this was a decision made by the ESLint team)
• Expose ESLint's --fix command line flag #​540 standard-engine/#​107
  • Lightweight, no additional dependencies, fixes dozens of rules automatically

New rules

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

• Enforce placing object properties on separate lines (object-property-newline) #​524 (2%)
• Require block comments to be balanced (spaced-comment "balanced") #​572 (2%)
• Disallow constant expressions in conditions (no-constant-condition) #​563 (1%)
• Disallow renaming import, export, and destructured assignments to the same name (no-useless-rename) #​537 (0%)
• Disallow spacing between rest and spread operators and their expressions (rest-spread-spacing) #​567 (0%)
• Disallow the Unicode Byte Order Mark (BOM) (unicode-bom) #​538 (0%)
• Disallow assignment to native objects/global variables (no-global-assign) #​596 (0%)
• Disallow negating the left operand of relational operators (no-unsafe-negation) #​595 (0%)
• Disallow template literal placeholder syntax in regular strings (no-template-curly-in-string) #​594 (0%)
• Disallow tabs in file (no-tabs) #​593 (0%)

Changed rules

• Relax rule: Allow template literal strings (backtick strings) to avoid escaping
 #​421
• Relax rule: Do not enforce spacing around * in generator functions (#​564 (comment))
  • This is a temporary workaround for babel users who use async generator functions.

v7.1.2

Compare Source

• Fix install errors for some users by updating eslint peer dependency

v7.1.1

Compare Source

• Add back full node 0.10, 0.12 support

v7.1.0

Compare Source

• Upgrade eslint to version ~2.10.2

v7.0.1

Compare Source

• Relax "no-duplicate-imports" rule to not include export so the following is allowed:

import { foo } from 'bar'
export * from 'bar'

v7.0.0

Compare Source

Changes

• Upgrade eslint to version ~2.9.0
• Remove "rules" configuration option #​367 from package.json (Reasoning is here)

New rules

Estimated % of affected standard users, based on test suite

• Require camelCase (camelcase) [4%]
• Disallow unnecessary escape usage (no-useless-escape) [4% -- but, including many bugs]
• Disallow duplicate imports (no-duplicate-imports) [0%]
• Disallow unmodified conditions of loops (no-unmodified-loop-condition) [0%]
• Disallow whitespace before properties (no-whitespace-before-property) [0%]
• Disallow control flow statements in finally blocks (no-unsafe-finally) [0%]
• Disallow unnecessary computed property keys on objects (no-useless-computed-key) [0%]
• Validate spacing before closing bracket in JSX (react/jsx-space-before-closing) [0%]

Removed rules

• Require parens in arrow function arguments (arrow-parens)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot. View repository job log here.

[renovate]

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 13.x releases. However, if you upgrade to 13.x manually then Renovate will then reenable updates for minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.