Search code, repositories, users, issues, pull requests...

What's Changed

fix: respect global ignores when scanning for vue files to lint by @haoqunjiang in #239
feat: support ESLint 10 as peer dependency

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

`v14.6.0`

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`

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`

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`

What's Changed

A tsSyntaxInTemplates configuration field, so that linting can be sped up by disabling it by @haoqunjiang in #142
Proper handling of the extends field, which is supported in typescript-eslint, fixes #136 by @haoqunjiang in #143

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

`v14.3.0`

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

fix: typo in index.ts by @aparajita in #128

New Contributors

@aparajita made their first contribution in #128

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

`v14.2.0`

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

@markieo1 made their first contribution in #108

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

`v14.1.4`

`v14.1.3`

What's Changed

docs: add missing curly bracket in example config by @henribru in #93
fix: skip typechecking cjs and mjs files by @henribru in #94

New Contributors

@henribru made their first contribution in #93

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

`v14.1.2`

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`

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`

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

@jfrs made their first contribution in #90

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

`v14.0.1`

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

@bmulholland made their first contribution in #84
@50Wliu made their first contribution in #86

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

`v14.0.0`

What's Changed

Added support for ESLint Flat Config #81
Dropped support for the legacy .eslintrc* configuration format. If you need that, please stay on version 13, which is also tagged as @vue/eslint-config-typescript@legacy-eslintrc.
The default configuration now extends from tseslint.configs.recommended instead of eslint-recommended.

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

Configuration

📅 Schedule: (UTC)

Branch creation
- Between 12:00 AM and 03:59 AM (* 0-3 * * *)
Automerge
- At any time (no schedule defined)

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

♻ Rebasing: Whenever PR is behind base branch, 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.

renovate · 2024-12-12T20:42:58Z

⚠️ 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: Rnwood.Smtp4dev/ClientApp/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: clientapp@1.0.0
npm error Found: eslint@8.57.1
npm error node_modules/eslint
npm error   dev eslint@"^8.57.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^9.10.0 || ^10.0.0" from @vue/eslint-config-typescript@14.7.0
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 /runner/cache/others/npm/_logs/2026-04-08T16_51_22_705Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-08T16_51_22_705Z-debug-0.log

github-actions · 2025-09-08T19:30:34Z

✅ All contributors have signed the CLA!

Thank you for signing the Contributor License Agreement. Your contribution can now be reviewed and merged! 🚀
_{Posted by the CLA Assistant Lite bot.}

sonarqubecloud · 2025-10-08T05:29:58Z

Quality Gate passed

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

sonarqubecloud · 2025-12-19T20:53:49Z

Quality Gate passed

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

sonarqubecloud · 2026-02-09T19:17:28Z

Quality Gate passed

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

sonarqubecloud · 2026-03-15T19:51:46Z

Quality Gate passed

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code