chore(deps): update dependency @vue/eslint-config-typescript to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@vue/eslint-config-typescript	4.0.0 -> 13.0.0

---

Release Notes

vuejs/eslint-config-typescript (@​vue/eslint-config-typescript)

v13.0.0

Compare Source

Notable Changes

typescript-eslint is upgraded to v7.x. The full release notes can be found in their release blog: https://typescript-eslint.io/blog/announcing-typescript-eslint-v7

It's a small major release that only updates some peer dependency version requirements:

• Requires Node.js >= 18.18, TypeScript >= 4.7.4, ESLint >= 8.56

v12.0.0

Compare Source

Notable Changes

typescript-eslint is upgraded to v6.x. The full release notes can be found in their release blog: https://typescript-eslint.io/blog/announcing-typescript-eslint-v6/
Here are some notable changes you might encounter when upgrading @vue/eslint-config-typescript from v11 to v12:

• Requires Node.js >= 16, TypeScript >= 4.2.4, ESLint >= 7
• The default config:
  • valid-typeof rule is re-enabled because it's not always covered by TypeScript
• The recommended config:
  • No longer includes stylistic rules; because the upstream @typescript-eslint/eslint-plugin has split them into standalone configs.
  • Some rules' severity levels are changed from warn to error, such as @typescript-eslint/no-unused-vars.
  • A more complete list of changes can be found at https://github.com/typescript-eslint/typescript-eslint/discussions/6014

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

Breaking Changes

• Bump eslint-plugin-vue to v9
• Drop Node.js v12 support

Other Notable Changes

• Use multiple parsers for more precise checking, and potentially improves performance (8c3628c)

v10.0.0

Compare Source

Breaking Change

• @typescript-eslint/* becomes dependencies instead of peer dependencies. It's because we now recommend using this package along with @rushstack/eslint-patch.

v9.1.0

Compare Source

• feat: allow using const foo = require('foo') in plain CommonJS modules (109b3f8)

v9.0.1

Compare Source

• Fixes the peer dependency version of eslint-plugin-vue (#​37) (@​2malh)

v9.0.0

Compare Source

• Upgrade vue-eslint-parser to v8;
• Drop support for Node.js < v12.22.0, v13, >=v14 < v14.17.0, v15

v8.0.0

Compare Source

• Supports ESLint 8
• Requires ESLint >= 6.2
• Requires @typescript-eslint/* >= 5.0
• Requires eslint-plugin-vue >= 7.17

Thanks to @​cexbrayat

v7.0.0

Compare Source

Update to @typescript-eslint/* v4.

See detailed breaking changes at https://github.com/typescript-eslint/typescript-eslint/releases/tag/v4.0.0

v6.0.0

Compare Source

Update to @​typescript-eslint/* v3. See detailed breaking changes at https://github.com/typescript-eslint/typescript-eslint/releases/tag/v3.0.0

The most notable ones are:

• Dropped support for Node version 8
• Dropped support for TypeScript 3.2

Check out the linked issues for more information about added/removed rules:

• @vue/typescript: https://github.com/typescript-eslint/typescript-eslint/issues/1273
• @vue/typescript/recommended: https://github.com/typescript-eslint/typescript-eslint/issues/1423

v5.1.0

Compare Source

Accept eslint@7 & eslint-plugin-vue@7 as peer dependencies

v5.0.2

Compare Source

Fix parser loading in Yarn 2 #​8

v5.0.1

Compare Source

Fix the Cannot read config file error for the recommended ruleset https://github.com/vuejs/eslint-config-typescript/pull/6

v5.0.0

• Updated typescript-eslint to v2, see the changelog at https://github.com/typescript-eslint/typescript-eslint/releases/tag/v2.0.0
• @typescript-eslint/eslint-plugin and @typescript-eslint/parser are now peer dependencies
• A new recommended ruleset

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone Europe/Stockholm, 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 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: client/package-lock.json

npm ERR! code ENOTSUP
npm ERR! notsup Unsupported engine for @vue/[email protected]: wanted: {"node":"^18.18.0 || >=20.0.0"} (current: {"node":"14.21.3","npm":"6.14.18"})
npm ERR! notsup Not compatible with your version of node/npm: @vue/[email protected]
npm ERR! notsup Not compatible with your version of node/npm: @vue/[email protected]
npm ERR! notsup Required: {"node":"^18.18.0 || >=20.0.0"}
npm ERR! notsup Actual:   {"npm":"6.14.18","node":"14.21.3"}

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-04-30T22_22_21_520Z-debug.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 13.x releases. But if you manually upgrade to 13.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.