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:
3.6.1
->3.7.0
12.0.0
->12.1.1
0.8.0
->0.11.1
56.0.0
->56.0.1
0.4.1
->0.5.4
3.2.5
->3.4.2
Release Notes
import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.7.0
Compare Source
Minor Changes
#326
93ea130
Thanks @SukkaW! - This version has implemented theeslint-plugin-import-x
's v3 resolver interface. This allows you to use import/require to referenceeslint-import-resolver-typescript
directly in your ESLint flat config:Previously
Now
Note that this only works with
eslint-plugin-import-x@>=4.5.0
. You can't usecreateTypeScriptImportResolver
with the older versions ofeslint-plugin-import-x
or any existing versions ofeslint-plugin-import
.v3.6.3
Compare Source
Patch Changes
#305
f8d7b82
Thanks @SukkaW! - Fix resolve fornode:test
,node:sea
, andnode:sqlite
without sacrificing installation size#288
a4c6c78
Thanks @SunsetTechuila! - fix: ignore bun built-in moduleslydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)
v12.1.1
Compare Source
This release adds a short
meta.docs.description
to each rule. Thanks to fisker Cheung (@fisker)!v12.1.0
Compare Source
This release adds TypeScript type definitions for the plugin itself. This is useful when you use TypeScript to check your ESLint configuration. It assumes that you install
@types/eslint
yourself. Thanks to @Logicer16!storybookjs/eslint-plugin-storybook (eslint-plugin-storybook)
v0.11.1
Compare Source
🐛 Bug Fix
Authors: 1
v0.11.0
Compare Source
🚀 Enhancement
🐛 Bug Fix
Authors: 2
v0.10.2
Compare Source
🐛 Bug Fix
Authors: 1
v0.10.1
Compare Source
🐛 Bug Fix
Authors: 1
v0.10.0
Compare Source
🚀 Enhancement
Authors: 3
v0.9.0
Compare Source
🚀 Enhancement
🐛 Bug Fix
generate-rule
#147 (@yinm)Authors: 3
sindresorhus/eslint-plugin-unicorn (eslint-plugin-unicorn)
v56.0.1
Compare Source
expiring-todo-comments
: Fix compatibility with ESLint 9.15 (#2497)16b09d3
veritem/eslint-plugin-vitest (eslint-plugin-vitest)
v0.5.4
Compare Source
Features
v0.5.3
Compare Source
Bug Fixes
v0.5.2
Compare Source
Features
v0.5.1
Compare Source
Bug Fixes
v0.5.0
Compare Source
This version only supports flat config!
If you run into issues consider downgrading and opening an issue ofcourse.
Full Changelog: vitest-dev/eslint-plugin-vitest@v0.5.0...v0.5.0
prettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)<!-- Input --> <template> <button @​click="foo += 2">Click</button> </template> <!-- Prettier 3.4.0 --> <template> <button @​click="(foo += 2)">Click</button> </template> <!-- Prettier 3.4.1 --> <template> <button @​click="foo += 2">Click</button> </template>
v3.4.0
Compare Source
diff
🔗 Release Notes
v3.3.3
Compare Source
diff
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
Add parentheses for decorator expressions (#16458 by @y-schneider)
Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.
Support
@let
declaration syntax (#16474 by @sosukesuzuki)Adds support for Angular v18
@let
declaration syntax.Please see the following code example. The
@let
declaration allows you to define local variables within the template:For more details, please refer to the excellent blog post by the Angular Team: Introducing @let in Angular.
We also appreciate the Angular Team for kindly answering our questions to implement this feature.
v3.3.2
Compare Source
diff
Fix handlebars path expressions starts with
@
(#16358 by @Princeyadav05)v3.3.1
Compare Source
diff
Preserve empty lines in front matter (#16347 by @fisker)
Preserve explicit language in front matter (#16348 by @fisker)
Avoid line breaks in import attributes (#16349 by @fisker)
v3.3.0
Compare Source
diff
🔗 Release Notes
Configuration
📅 Schedule: Branch creation - "* * * * 1-5" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.