typist icon indicating copy to clipboard operation
typist copied to clipboard

chore(deps): update linters

Open renovate[bot] opened this issue 1 year ago • 1 comments

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-import-resolver-typescript 3.6.1 -> 3.10.1 age adoption passing confidence
eslint-plugin-simple-import-sort 12.0.0 -> 12.1.1 age adoption passing confidence
eslint-plugin-storybook 0.8.0 -> 0.12.0 age adoption passing confidence
eslint-plugin-unicorn 56.0.0 -> 56.0.1 age adoption passing confidence
eslint-plugin-vitest 0.4.1 -> 0.5.4 age adoption passing confidence
prettier (source) 3.2.5 -> 3.5.3 age adoption passing confidence

Release Notes

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v3.10.1

Compare Source

v3.10.0

Compare Source

Minor Changes

Full Changelog: https://github.com/import-js/eslint-import-resolver-typescript/compare/v3.9.1...v3.10.0

v3.9.1

Compare Source

Patch Changes

v3.9.0

Compare Source

Minor Changes

v3.8.7

Compare Source

Patch Changes

v3.8.6

Compare Source

Patch Changes

v3.8.5

Compare Source

Patch Changes

v3.8.4

Compare Source

Patch Changes

v3.8.3

Compare Source

Patch Changes

v3.8.2

Compare Source

Patch Changes

v3.8.1

Compare Source

Patch Changes

v3.8.0

Compare Source

Minor Changes
  • #​345 fcc8883 Thanks @​carlocorradini! - Enable the mapper function just for a set of allowed files. Improves project discovery using glob and POSIX separator.

  • #​346 c124e87 Thanks @​carlocorradini! - Update get-tsconfig to the the latest version. We now support the ${configDir} variable, introduced in TypeScript 5.5.

v3.7.0

Compare Source

Minor Changes
  • #​326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly 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 use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

v3.6.3

Compare Source

Patch Changes
lydell/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.12.0

Compare Source

🚀 Enhancement
Authors: 3

v0.11.6

Compare Source

🐛 Bug Fix
Authors: 1

v0.11.5

Compare Source

🐛 Bug Fix
Authors: 1

v0.11.4

Compare Source

🐛 Bug Fix
Authors: 1

v0.11.3

Compare Source

🐛 Bug Fix
📝 Documentation
🔩 Dependency Updates
Authors: 4

v0.11.2

Compare Source

🐛 Bug Fix
Authors: 2

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
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
  • support old Eslint configuration
  • update dependencies

v0.5.3

Compare Source

Bug Fixes

v0.5.2

Compare Source

Features

v0.5.1

Compare Source

Bug Fixes
  • no-focused-tests: support .each template strings (#​420) (36e5b9a)

v0.5.0

Compare Source

‼️ 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

Compare Source

v3.5.2

Compare Source

diff

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

Compare Source

diff

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

Compare Source

diff

🔗 Release Notes

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.

<!-- 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 {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;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

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;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.

// 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
@&#8203;(foo`tagged template`)
class X {}

// Prettier 3.3.2
@&#8203;foo`tagged template`
class X {}

// Prettier 3.3.3
@&#8203;(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:

@&#8203;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

Compare Source

diff

Fix handlebars path expressions starts with @ (#​16358 by @​Princeyadav05)
{{! Input }}
<div>{{@&#8203;x.y.z}}</div>

{{! Prettier 3.3.1 }}
<div>{{@&#8203;x}}</div>

{{! Prettier 3.3.2 }}
<div>{{@&#8203;x.y.z}}</div>

v3.3.1

Compare Source

diff

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

Compare Source

diff

🔗 Release Notes


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.

renovate[bot] avatar Nov 04 '24 16:11 renovate[bot]

Deploy Preview for doist-typist failed.

Name Link
Latest commit 1c3ff8ba9ff4e8a89fac7ce17199d3242b32e010
Latest deploy log https://app.netlify.com/projects/doist-typist/deploys/68fc9a6693f502000849c599

netlify[bot] avatar Nov 04 '24 16:11 netlify[bot]

⚠️ 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

renovate[bot] avatar Jun 02 '25 08:06 renovate[bot]

Closing this since it depends on https://github.com/Doist/typist/pull/785.

rfgamaral avatar Oct 25 '25 09:10 rfgamaral