chore(deps): update dependency babel-eslint to v10 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
babel-eslint	8.2.2 -> 10.1.0

---

Release Notes

babel/babel-eslint (babel-eslint)

v10.1.0

Compare Source

• Added ability to parse Flow enums #​812 (@​gkz)

v10.0.3

Compare Source

Fixes https://github.com/babel/babel-eslint/issues/791, also https://github.com/eslint/eslint/issues/12117

Some context: https://github.com/babel/babel-eslint/pull/793#issuecomment-524435971

We ended up going with @​JLHwung's PR https://github.com/babel/babel-eslint/pull/794 which uses ESLint's deps instead of going with peerDeps since it really depends on the version being used and we don't want users to have to install it directly on their own.

babel-eslint is patching patches of the dependencies of ESLint itself so these kinds of issues have happened in the past. We'll need to look into figuring out how to have a more solid way of modifying behavior instead of this monkeypatching type of thing for future releases.

v10.0.2

Compare Source

Fixes https://github.com/babel/babel-eslint/issues/772

v10.0.1

Compare Source

v10.0.1

• Reverting https://github.com/babel/babel-eslint/pull/584

The TypeAlias "conversion" to a function has issues. Sounds like we need to rethink the change, most likely we can just actually change the scoping rather than hardcode an AST change.

v10.0.0

Compare Source

v10.0.0

Small breaking change: add a peerDependency starting from the ESLint version that added a parser feature that we were monkeypatching before (and drop that code). If already using ESLint 5 shouldn't be any different.

• Bugfix for TypeAlias: https://github.com/babel/babel-eslint/pull/584

/* @​flow */
type Node<T> = { head: T; tail: Node<T> }

// or 

type File = {chunks: Array<Chunk>}
type Chunk = {file: File}

• Update to test against ESLint 5, add a peerDependency: https://github.com/babel/babel-eslint/pull/689
• Drop monkeypatching behavior: https://github.com/babel/babel-eslint/pull/690

v9.0.0

Compare Source

v9.0.0

We've released v7: https://twitter.com/left_pad/status/1034204330352500736, so this just updates babel-eslint to use those versions internally. That in itself doesn't break anything but:

• Babel now supports the new decorators proposal by default, so we need to switch between the new and the old proposal. This is a breaking change.

To enable the legacy decorators proposal users should add a specific parser option:

{
  parserOptions: {
    ecmaFeatures: {
      legacyDecorators: true
    }
  }
}

• Babel removed the support for Node 4 , so I propagated that here.

v8.2.6

Compare Source

v8.2.5

Compare Source

v8.2.4

Compare Source

v8.2.3

Compare Source

---

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: Never, 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/babel-eslint
npm ERR!   dev babel-eslint@"10.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer babel-eslint@"^8.0.1" from [email protected]
npm ERR! node_modules/eslint-config-scratch
npm ERR!   dev eslint-config-scratch@"5.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/babel-eslint
npm ERR!   peer babel-eslint@"^8.0.1" from [email protected]
npm ERR!   node_modules/eslint-config-scratch
npm ERR!     dev eslint-config-scratch@"5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-16T00_29_57_633Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-16T00_29_57_633Z-debug-0.log