chore(deps): update dependency standard to v17

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
standard (source)	14.3.4 → 17.1.2

---

Release Notes

standard/standard (standard)

v17.1.2

Compare Source

• Unpin and bump eslint-plugin-react(#​1976) 004e63b

v17.1.1

Compare Source

• Pin eslint-plugin-react to 7.35.2 (#​1976) d535d98

v17.1.0

Compare Source

• Update eslint-config-standard from 17.0.0 to 17.1.0

v17.0.0

Compare Source

• Update eslint-config-standard from 17.0.0 to 17.1.0

v16.0.4

Compare Source

• Update eslint from ~7.13.1 to ~7.18.0
• Update eslint-config-standard from 16.0.2 to 16.0.3
• Update eslint-plugin-import from ~2.22.1 to ~2.24.2
• Update eslint-plugin-promise from ~4.2.1 to ~5.1.0
• Update eslint-plugin-react from ~7.21.5 to ~7.25.1

v16.0.3

Compare Source

We're super excited to announce standard 17!

This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.

When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.

This is the first release by two of our standard co-maintainers @​Divlo and @​voxpelli. Buy them a cake if you run into them, thanks for getting this release out!

Major changes

• eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.
• object-shorthand rule (as warning)
• Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #​1548 #​1775
• --verbose by default

Changed features

• Update eslint from ~7.18.0 to ^8.13.0
• Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
• Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
• Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
• Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
• Update eslint-plugin-import from ~2.24.2 to ^2.26.0
• Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
• Update eslint-plugin-react from ~7.25.1 to ^7.28.0

v16.0.2

Compare Source

• Update eslint from ~7.13.1 to ~7.18.0
• Update eslint-config-standard from 16.0.2 to 16.0.3
• Update eslint-plugin-import from ~2.22.1 to ~2.24.2
• Update eslint-plugin-promise from ~4.2.1 to ~5.1.0
• Update eslint-plugin-react from ~7.21.5 to ~7.25.1

v16.0.1

Compare Source

• Introduce "warning" system for disruptive rules (read more below)
• Change rule to a "warning": Require let or const instead of var (no-var) #​633

standard treats all rule violations as errors, which means that standard
will exit with a non-zero (error) exit code.

However, we may occasionally release a new major version of standard
which changes a rule that affects the majority of standard users (for example,
transitioning from var to let/const). We do this only when we think the
advantage is worth the cost and only when the rule is
auto-fixable.

In these situations, we have a "transition period" where the rule change is only
a "warning". Warnings don't cause standard to return a non-zero (error)
exit code. However, a warning message will still print to the console. During
the transition period, using standard --fix will update your code so that it's
ready for the next major version.

The slow and careful approach is what we strive for with standard. We're
generally extremely conservative in enforcing the usage of new language
features. We want using standard to be light and fun and so we're careful
about making changes that may get in your way. As always, you can
disable a rule at any time, if necessary.

v16.0.0

Compare Source

We're super excited to announce standard 16!

As with every new major release, there are lots of new rules in 16.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
better performance, tons of bug fixes, improved JSX, React ⚛️, and Next.js support!

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, please
support Feross!

New features

• 🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #​1023

  • Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with .gitignore

• 🌟 Support the .gitignore ignore syntax from the command line #​1117

  • In older versions, the command standard src would not lint the src/ folder
  • Instead, a glob pattern like standard src/**/*.js was required
  • This is now fixed! You can run standard src to lint the src/ folder!

• 🌟 Support relative paths from the command line in more situations (e.g. standard ../src/*.js) #​1384

• 🌟 New extensions option for linting additional extensions besides .js, .jsx, .mjs, and .cjs

  • Can be configured with the --ext command line flag or in package.json:

  • Example:

    standard --ext .ts

    {
      "standard": {
        "extensions": [".ts"]
      }
    }

• 🌟 New cache directory location, respecting XDG_CACHE_HOME preference, with fallback to ~/.cache/standard standard-engine/#​214

Changed features

• Update eslint from ~7.11.0 to ~7.12.1

• Update standard-engine from ^12 to ^14

  • Fix inaccurate --help command which indicates that bundle.js is automatically ignored when it is not anymore standard-engine/#​224
  • Remove deglob package and use built-in ESLint folder-traversal support

• Paths with square brackets (e.g. [ and ]) are no longer skipped #​1333

  • This pattern is particularly common in Next.js apps, e.g. blog/[slug].js
  • You may notice new errors in these files since they were not being linted before

• Better mono-repo support: Nested node_modules/ folders are ignored by default #​1182

• Remove eslint-plugin-standard #​1316

  • We migrated the remaining no-callback-literal rule into eslint-plugin-node

New rules

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

• Require let or const instead of var (no-var) #​633 [75%] [automatic fixing reduces to 11%]
• Enforce return statements in Array method callbacks (array-callback-return) #​859 [7%]
• Disallow empty block statements (no-empty) #​796 [2%]
• Enforce default parameters to be last (default-param-last) #​1414 [1%]
• Disallow use of the RegExp constructor in favor of regular expression literals (prefer-regex-literals) #​1413 [1%]
• Disallow spaces inside of computed keys of class methods, getters and setters (computed-property-spacing) #​1416 [0%]
• Disallow case NaN, switch(NaN), indexOf(NaN), and lastIndexOf(NaN) (use-isnan) #​1429 [0%]
• Disallow assigning to imported bindings (no-import-assign) #​1412 [0%]
• Enforce getter/setter pairs in classes (accessor-pairs) #​1415 [0%]
• Node: Disallow assignment to exports (node/no-exports-assign) #​1400 [0%]
• React: Prevent usage of the return value of ReactDOM.render (react/no-render-return-value) #​1568 [1%]
• React: Prevent usage of deprecated methods (react/no-deprecated) #​1572 [1%]
• React: Prevent direct mutation of this.state (react/no-direct-mutation-state) #​1571 [0%]
• React: Prevent usage of findDOMNode (react/no-find-dom-node) #​1570 [0%]
• React: Prevent usage of isMounted (react/no-is-mounted) #​1569 [0%]
• React: Prevent using string refs (react/no-string-refs) #​1567 [0%]
• JSX: Prevent missing parentheses around multiline JSX (react/jsx-wrap-multilines) #​710 #​1382 (0%)
• JSX: Check if shorthand fragment syntax requires a key prop (react/jsx-key) #​1575 [0%]
• JSX: Prevent passing of children as props (react/no-children-prop) #​1574 [0%]
• JSX: Prevent using children and dangerouslySetInnerHTML as props at the same time (react/no-danger-with-children) #​1573 [0%]
• JSX: Prevent invalid characters from appearing in markup (react/no-unescaped-entities) #​1566 [0%]
• JSX: Enforce JSX value is returned in component render function (react/require-render-return) #​1565 [0%]
• JSX: Prevent usage of unsafe target='_blank' on any component named Link (react/jsx-no-target-blank) #​1576 [0%]

Changed rules

• Relax rule: JSX: Consider the global scope when checking for defined Components #​1115
• Relax rule: JSX: Remove conflicting indentation rule in indent #​1499

v15.0.1

Compare Source

• Relax rule: Remove conflicting JSX indenting with indent rule eslint-config-standard/#​177

v15.0.0

Compare Source

We're super excited to announce standard 17!

This major release fully focuses on getting in sync with the wider ESLint ecosystem
and doesn't in itself introduce any new rules or features.

When you upgrade, consider running standard --fix to automatically format your
code to match the current set of rules.

This is the first release by two of our standard co-maintainers @​Divlo and @​voxpelli. Buy them a cake if you run into them, thanks for getting this release out!

Major changes

• eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.
• object-shorthand rule (as warning)
• Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level await #​1548 #​1775
• --verbose by default

Changed features

• Update eslint from ~7.18.0 to ^8.13.0
• Update eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8
• Update eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8
• Update standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOG
• Move from eslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8
• Update eslint-plugin-import from ~2.24.2 to ^2.26.0
• Update eslint-plugin-promise from ~5.1.0 to ^6.0.0
• Update eslint-plugin-react from ~7.25.1 to ^7.28.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 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 was generated by Mend Renovate. View the repository job log.