chore(deps): update linters
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| eslint-import-resolver-typescript | 3.6.1 -> 3.10.1 |
||||
| eslint-plugin-simple-import-sort | 12.0.0 -> 12.1.1 |
||||
| eslint-plugin-storybook | 0.8.0 -> 0.12.0 |
||||
| eslint-plugin-unicorn | 56.0.0 -> 56.0.1 |
||||
| eslint-plugin-vitest | 0.4.1 -> 0.5.4 |
||||
| prettier (source) | 3.2.5 -> 3.5.3 |
Release Notes
import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.10.1
v3.10.0
Minor Changes
-
#413
89c2795Thanks @JounQin! - chore: housekeeping, bump all (dev) depsMigrate
rspack-resolverto rebrandingunrs-resolverfor more targets support and other bug fixes
Full Changelog: https://github.com/import-js/eslint-import-resolver-typescript/compare/v3.9.1...v3.10.0
v3.9.1
Patch Changes
- #382
4a9176eThanks @JounQin! - fix: userspack-resolverfork for pnp support
v3.9.0
Minor Changes
v3.8.7
Patch Changes
- #377
a14fdd9Thanks @carlocorradini! - fix: include mapper with no files and force non-dynamic projects to use absolute paths
v3.8.6
Patch Changes
v3.8.5
Patch Changes
- #372
366eeafThanks @carlocorradini! - fix: if file has no corresponding mapper function, apply all of them, starting with the nearest one.
v3.8.4
Patch Changes
v3.8.3
Patch Changes
-
#360
8192976Thanks @carlocorradini! - Force tiniglobby to expand dot directories -
#360
8192976Thanks @carlocorradini! - Update tinyglobby to latest version
v3.8.2
Patch Changes
- #357
5fd349eThanks @carlocorradini! - Update thetinyglobbyto the latest version to solve performance regressions.
v3.8.1
Patch Changes
- #352
0c6303dThanks @carlocorradini! - Set cwd while resolving tsconfig include
v3.8.0
Minor Changes
-
#345
fcc8883Thanks @carlocorradini! - Enable the mapper function just for a set of allowed files. Improves project discovery using glob and POSIX separator. -
#346
c124e87Thanks @carlocorradini! - Update get-tsconfig to the the latest version. We now support the${configDir}variable, introduced in TypeScript 5.5.
v3.7.0
Minor Changes
-
#326
93ea130Thanks @SukkaW! - This version has implemented theeslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to referenceeslint-import-resolver-typescriptdirectly in your ESLint flat config:Previously
// eslint.config.js module.exports = { settings: { 'import-x/resolver': { typescript: { alwaysTryTypes: true, }, // or require.resolve('eslint-import-resolver-typescript'): alwaysTryTypes: true, } } } }Now
// eslint.config.js const { createTypeScriptImportResolver, } = require('eslint-import-resolver-typescript') module.exports = { settings: { 'import-x/resolver-next': [ createTypeScriptImportResolver({ alwaysTryTypes: true, }), ], }, }Note that this only works with
eslint-plugin-import-x@>=4.5.0. You can't usecreateTypeScriptImportResolverwith the older versions ofeslint-plugin-import-xor any existing versions ofeslint-plugin-import.
v3.6.3
Patch Changes
lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)
v12.1.1
This release adds a short meta.docs.description to each rule. Thanks to fisker Cheung (@fisker)!
v12.1.0
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.12.0
🚀 Enhancement
- Add meta-satisfies-type rule (rebased) #200 (@NotWoods @Sidnioulz @kasperpeulen)
Authors: 3
- Kasper Peulen (@kasperpeulen)
- Steve Dodier-Lazaro (@Sidnioulz)
- Tiger Oakes (@NotWoods)
v0.11.6
🐛 Bug Fix
Authors: 1
- Makoto Tateno (@makotot)
v0.11.5
🐛 Bug Fix
- fix(peer-deps): Add support for typescript 5.8 #195 (@mrginglymus)
Authors: 1
- Bill Collins (@mrginglymus)
v0.11.4
🐛 Bug Fix
- feat: Support storybook/test for expect imports #194 (@valentinpalkovic)
Authors: 1
- Valentin Palkovic (@valentinpalkovic)
v0.11.3
🐛 Bug Fix
- Upgrade corepack/pnpm #191 (@kasperpeulen)
- default-exports: Support CSF factory style meta #187 (@yannbf)
📝 Documentation
- docs: Explicitly mention flat config for findability #190 (@Sidnioulz)
🔩 Dependency Updates
- fix(deps): add typescript as a peer dependency #189 (@TomKalina)
Authors: 4
- Kasper Peulen (@kasperpeulen)
- Steve Dodier-Lazaro (@Sidnioulz)
- Tonda (Tomáš) Kalina (@TomKalina)
- Yann Braga (@yannbf)
v0.11.2
🐛 Bug Fix
Authors: 2
v0.11.1
🐛 Bug Fix
- Type configs using literal types #182 (@ethanwu10)
Authors: 1
- Ethan Wu (@ethanwu10)
v0.11.0
🚀 Enhancement
🐛 Bug Fix
- Update docs to be more clear about extended categories #179 (@yannbf)
- chore: Update the link for eslintignore doc #163 (@tunawasabi)
Authors: 2
- wasabi (@tunawasabi)
- Yann Braga (@yannbf)
v0.10.2
🐛 Bug Fix
- Fix: Bring back non-categorized rules #176 (@yannbf)
- Build: Refactor, fix issues reported by eslint and format md files #175 (@yannbf)
Authors: 1
- Yann Braga (@yannbf)
v0.10.1
🐛 Bug Fix
- Bump CSF version to remove lodash transitive dep #171 (@kasperpeulen)
Authors: 1
- Kasper Peulen (@kasperpeulen)
v0.10.0
🚀 Enhancement
- feat: support flat config #156 (@kazupon @yannbf @kasperpeulen)
Authors: 3
- Kasper Peulen (@kasperpeulen)
- kazuya kawaguchi (@kazupon)
- Yann Braga (@yannbf)
v0.9.0
🚀 Enhancement
🐛 Bug Fix
- Tweak
generate-rule#147 (@yinm) - Update links in docs #130 (@hoonweiting @yannbf)
- Remove uninformative 'Further Reading' sections from rule docs #131 (@hoonweiting)
Authors: 3
- Wei Ting (@hoonweiting)
- Yann Braga (@yannbf)
- Yusuke Iinuma (@yinm)
sindresorhus/eslint-plugin-unicorn (eslint-plugin-unicorn)
v56.0.1
veritem/eslint-plugin-vitest (eslint-plugin-vitest)
v0.5.4
Features
- support old Eslint configuration
- update dependencies
v0.5.3
Bug Fixes
v0.5.2
Features
v0.5.1
Bug Fixes
v0.5.0
‼️ Breaking Change 🚨
This version only supports new eslint flat config!
If you run into issues, consider downgrading and opening an issue. Remember to include a minimum repro example to help me fix issues quickly!
Full Changelog: https://github.com/veritem/eslint-plugin-vitest/compare/v0.5.0...v0.5.0
prettier/prettier (prettier)
v3.5.3
v3.5.2
Remove module-sync condition (#17156 by @fisker)
In Prettier 3.5.0, we added module-sync condition to package.json, so that require("prettier") can use ESM version, but turns out it doesn't work if CommonJS and ESM plugins both imports builtin plugins. To solve this problem, we decide simply remove the module-sync condition, so require("prettier") will still use the CommonJS version, we'll revisit until require(ESM) feature is more stable.
v3.5.1
Fix CLI crash when cache for old version exists (#17100 by @sosukesuzuki)
Prettier 3.5 uses a different cache format than previous versions, Prettier 3.5.0 crashes when reading existing cache file, Prettier 3.5.1 fixed the problem.
Support dockercompose and github-actions-workflow in VSCode (#17101 by @remcohaszing)
Prettier now supports the dockercompose and github-actions-workflow languages in Visual Studio Code.
v3.5.0
v3.4.2
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.
<!-- Input (--prose-wrap=never) -->
C言
語
・
C++
・
Go
・
Rust
<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust
<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust
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)
// Input
class A {
@​decorator
/**
* The method description
*
*/
async method(foo: Foo, bar: Bar) {
console.log(foo);
}
}
// Prettier 3.4.1
class A {
@​decorator
async /**
* The method description
*
*/
method(foo: Foo, bar: Bar) {
console.log(foo);
}
}
// Prettier 3.4.2
class A {
@​decorator
/**
* The method description
*
*/
async method(foo: Foo, bar: Bar) {
console.log(foo);
}
}
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.
// Input
<div>
foo
<span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
, abc
</div>;
// Prettier 3.4.1 (first)
<div>
foo
<span>
longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
</span>, abc
</div>;
// Prettier 3.4.1 (second)
<div>
foo
<span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
, abc
</div>;
// Prettier 3.4.2
<div>
foo
<span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
, abc
</div>;
v3.4.1
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
v3.3.3
Add parentheses for nullish coalescing in ternary (#16391 by @cdignam-segment)
This change adds clarity to operator precedence.
// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);
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.
// Input
@​(foo`tagged template`)
class X {}
// Prettier 3.3.2
@​foo`tagged template`
class X {}
// Prettier 3.3.3
@​(foo`tagged template`)
class X {}
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:
@​let name = 'Frodo';
<h1>Dashboard for {{name}}</h1>
Hello, {{name}}
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
Fix handlebars path expressions starts with @ (#16358 by @Princeyadav05)
{{! Input }}
<div>{{@​x.y.z}}</div>
{{! Prettier 3.3.1 }}
<div>{{@​x}}</div>
{{! Prettier 3.3.2 }}
<div>{{@​x.y.z}}</div>
v3.3.1
Preserve empty lines in front matter (#16347 by @fisker)
<!-- Input -->
---
foo:
- bar1
- bar2
- bar3
---
Markdown
<!-- Prettier 3.3.0 -->
---
foo:
- bar1
- bar2
- bar3
---
Markdown
<!-- Prettier 3.3.1 -->
---
foo:
- bar1
- bar2
- bar3
---
Markdown
Preserve explicit language in front matter (#16348 by @fisker)
<!-- Input -->
---yaml
title: Hello
slug: home
---
<!-- Prettier 3.3.0 -->
---
title: Hello
slug: home
---
<!-- Prettier 3.3.1 -->
---yaml
title: Hello
slug: home
---
Avoid line breaks in import attributes (#16349 by @fisker)
// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };
// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
"json" };
// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };
v3.3.0
Configuration
📅 Schedule: Branch creation - Monday through Friday ( * * * * 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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Deploy Preview for doist-typist failed.
| Name | Link |
|---|---|
| Latest commit | 1c3ff8ba9ff4e8a89fac7ce17199d3242b32e010 |
| Latest deploy log | https://app.netlify.com/projects/doist-typist/deploys/68fc9a6693f502000849c599 |
⚠️ 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: 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 could not resolve
npm error
npm error While resolving: @doist/[email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error @typescript-eslint/utils@"6.21.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error peer @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from @doist/[email protected]
npm error node_modules/@doist/eslint-config
npm error dev @doist/eslint-config@"11.2.0" from the root project
npm error @typescript-eslint/utils@"6.21.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/type-utils
npm error @typescript-eslint/type-utils@"6.21.0" from @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/eslint-plugin
npm error peer @typescript-eslint/eslint-plugin@"^6.0.0 || ^7.0.0 || ^8.0.0" from @doist/[email protected]
npm error node_modules/@doist/eslint-config
npm error dev @doist/eslint-config@"11.2.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev eslint-import-resolver-typescript@"3.10.1" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error peerOptional @typescript-eslint/utils@"^8.0.0" from [email protected]
npm error node_modules/eslint-plugin-import-x
npm error peerOptional eslint-plugin-import-x@"*" from [email protected]
npm error node_modules/eslint-import-resolver-typescript
npm error dev eslint-import-resolver-typescript@"3.10.1" 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/2025-10-25T09_40_27_279Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-25T09_40_27_279Z-debug-0.log
Closing this since it depends on https://github.com/Doist/typist/pull/785.