Skip to content

Conversation

a-klos
Copy link
Member

@a-klos a-klos commented Oct 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@vue/eslint-config-typescript ^11.0.3 -> ^14.0.0 age confidence

Release Notes

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

v14.6.0

Compare Source

New Features

  • feat: allowComponentTypeUnsafety option to configure the strictness of no-unsafe-* rules by @​haoqunjiang in #​185

Full Changelog: vuejs/eslint-config-typescript@v14.5.1...v14.6.0

v14.5.1

Compare Source

Notable Changes

  • fix: ensure there's only one instance of eslint-plugin-vue in the config, to avoid Cannot redefine plugin "vue" errors by @​haoqunjiang in #​184

Full Changelog: vuejs/eslint-config-typescript@v14.5.0...v14.5.1

v14.5.0

Compare Source

What's Changed

  • chore(deps): update dependency vue-eslint-parser to v10 by @​renovate in #​157
  • chore(deps): expand peer dependency eslint-plugin-vue version range to allow v10 by @​renovate in #​156

Full Changelog: vuejs/eslint-config-typescript@v14.4.0...v14.5.0

v14.4.0

Compare Source

What's Changed

Full Changelog: vuejs/eslint-config-typescript@v14.3.0...v14.4.0

v14.3.0

Compare Source

New Features

  • A completely new approach to set up the ESLint configurations with helpers like defineConfigWithVueTs and vueTsConfigs.
    Please read the documentation for more details.
    With this new API set, you can easily override type-aware linting rules without worrying its position in the config array. Therefore there would be fewer mysterious errors or slowdown in a heavily customized project.

[!NOTE]
The old style ...vueTsEslintConfig() still works, there's no need to update to the new style if that has been working well in your project.

Bug Fixes

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.2.0...v14.3.0

v14.2.0

Compare Source

What's Changed

  • fix: add absolute path for reading file contents, fix rootDir issue by @​markieo1 in #​108
  • feat: add a defineConfig utility function and use it in examples by @​haoqunjiang in #​117 Don't use this feature yet, it's under active refactoring for better usability.

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.1.4...v14.2.0

v14.1.4

Compare Source

v14.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.1.2...v14.1.3

v14.1.2

Compare Source

Bug Fixes

  • Print more friendly error messages if the user provides a non-existent configuration name to extends.

Full Changelog: vuejs/eslint-config-typescript@v14.1.1...v14.1.2

v14.1.1

Compare Source

Bug Fixes

  • Fixed #​91

    TypeError: Config "typescript-eslint/disable-type-checked": Key "files": Expected value to be a non-empty array"

Full Changelog: vuejs/eslint-config-typescript@v14.1.0...v14.1.1

v14.1.0

Compare Source

New Features

  • feat: simplify the *TypeChecked configs by providing a meaningful and performant default by @​haoqunjiang in #​89

Bug Fixes

  • fix: add the missing dot to extraFileExtensions by @​jfrs in #​90

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.0.1...v14.1.0

v14.0.1

Compare Source

Bugfixes

  • Fixed an occasional bug that when using with npm or yarn v1, an invalid ecmaVersion error would be thrown if the wrong version of estree is hoisted to the node_modules root. Fixes #​87. [aae95d6]

New Contributors

Full Changelog: vuejs/eslint-config-typescript@v14.0.0...v14.0.1

v14.0.0

Compare Source

What's Changed

Full Changelog: vuejs/eslint-config-typescript@v13.0.0...v14.0.0

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:


Configuration

📅 Schedule: Branch creation - "before 4am" in timezone UTC, 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 Renovate Bot.

@a-klos
Copy link
Member Author

a-klos commented Oct 5, 2025

⚠️ 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: services/frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"8.57.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^9.10.0" from @vue/[email protected]
npm error node_modules/@vue/eslint-config-typescript
npm error   dev @vue/eslint-config-typescript@"^14.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-10-05T01_30_56_245Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-10-05T01_30_56_245Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants