Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.19.1
->6.21.0
6.19.1
->6.21.0
6.1.0
->6.1.1
0.43.1
->0.44.0
0.3.20
->0.3.21
3.2.4
->3.2.5
Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v6.21.0
Compare Source
🚀 Features
export plugin metadata
allow
parserOptions.project: false
eslint-plugin: add rule prefer-find
🩹 Fixes
eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression
eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values
eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions
eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option
eslint-plugin: [class-literal-property-style] allow getter when same key setter exists
eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before
as
keyword❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0
Compare Source
🚀 Features
🩹 Fixes
eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result
eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable
eslint-plugin: [no-useless-template-literals] report Infinity & NaN
eslint-plugin: [prefer-readonly] disable checking accessors
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v6.21.0
Compare Source
🚀 Features
parserOptions.project: false
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
avajs/ava (ava)
v6.1.1
Compare Source
What's Changed
Full Changelog: avajs/ava@v6.1.0...v6.1.1
xojs/eslint-config-xo (eslint-config-xo)
v0.44.0
Compare Source
Breaking
f2060de
New rules
logical-assignment-operators
27049c1
prefer-object-has-own
288a3ca
object-curly-newline
(#83)3a5448b
Improvements
atob
andbtoa
dfa969c
no-new-object
rule7f8f92e
no-unused-vars
: Allow ignoring variables by prefixing with underscoreb31ab8a
veritem/eslint-plugin-vitest (eslint-plugin-vitest)
v0.3.21
Compare Source
What's Changed
New Contributors
Full Changelog: vitest-dev/eslint-plugin-vitest@v0.3.20...v0.3.21
prettier/prettier (prettier)
v3.2.5
Compare Source
diff
Support Angular inline styles as single template literal (#15968 by @sosukesuzuki)
Angular v17 supports single string inline styles.
Unexpected embedded formatting for Angular template (#15969 by @JounQin)
Computed template should not be considered as Angular component template
Use
"json"
parser fortsconfig.json
by default (#16012 by @sosukesuzuki)In v2.3.0, we introduced
"jsonc"
parser which adds trialing comma by default.When adding a new parser we also define how it will be used based on the
linguist-languages
data.tsconfig.json
is a special file used by TypeScript, it uses.json
file extension, but it actually uses the JSON with Comments syntax. However, we found that there are many third-party tools not recognize it correctly because of the confusing.json
file extension.We decide to treat it as a JSON file for now to avoid the extra configuration step.
To keep using the
"jsonc"
parser for yourtsconfig.json
files, add the following to your.pretterrc
fileConfiguration
📅 Schedule: Branch creation - "every weekend" (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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.