chore(deps): update all non-major dependencies #268

renovate · 2024-12-31T11:30:31Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/js (source)	`^9.16.0` -> `^9.17.0`
@types/node (source)	`~20.17.9` -> `~20.17.10`
@typescript-eslint/eslint-plugin (source)	`^8.18.0` -> `^8.19.0`
@typescript-eslint/parser (source)	`^8.18.0` -> `^8.19.0`
@vitest/coverage-v8 (source)	`^2.1.6` -> `^2.1.8`
chalk	`^5.3.0` -> `^5.4.1`
esbuild	`^0.24.0` -> `^0.24.2`
eslint (source)	`^9.16.0` -> `^9.17.0`
eslint-plugin-import-x	`^4.5.0` -> `^4.6.1`
pnpm (source)	`9.14.4` -> `9.15.2`
prettier (source)	`3.4.1` -> `3.4.2`
typescript-eslint (source)	`^8.18.0` -> `^8.19.0`
vitest (source)	`^2.1.6` -> `^2.1.8`

Release Notes

eslint/eslint (@eslint/js)

`v9.17.0`

Compare Source

Features

eed91d1 feat: add suggestions to no-unused-vars (#18352) (Tanuj Kanti)

Bug Fixes

67d683d fix: fix crash when message.fix is nullish (#19168) (ntnyq)
c618707 fix: ignore vars with non-identifier references in no-useless-assignment (#19200) (YeonJuan)

Documentation

3c22d2a docs: update yoda to Yoda in yoda.md for consistency (#19230) (루밀LuMir)
e0a2203 docs: add missing backticks to no-sequences (#19233) (루밀LuMir)
4cc4881 docs: Update README (GitHub Actions Bot)
3db6fdf docs: [no-await-in-loop] expand on benefits and inapplicability (#19211) (Kirk Waiblinger)
bf2a4f6 docs: add missing backticks to func-style (#19227) (루밀LuMir)
ba098bd docs: add missing header to prefer-spread (#19224) (루밀LuMir)
b607ae6 docs: update description of no-param-reassign (#19220) (루밀LuMir)
1eb424d docs: add missing backticks to prefer-destructuring (#19223) (루밀LuMir)
85998d1 docs: add missing backticks to no-unneeded-ternary (#19222) (루밀LuMir)
b75b32c docs: add missing backticks to no-new-func (#19219) (루밀LuMir)
a7700bc docs: add missing backticks to id-length (#19217) (루밀LuMir)
e2bb429 docs: add missing backticks to complexity.md (#19214) (루밀LuMir)
045d716 docs: add missing ) to id-denylist (#19213) (루밀LuMir)
7fe4114 docs: Update README (GitHub Actions Bot)
c743ba6 docs: add CSS language to no-restricted-syntax (#19208) (Milos Djermanovic)
1416d70 docs: add missing backticks to eqeqeq (#19207) (루밀LuMir)
b950c1b docs: add missing backticks to prefer-object-spread (#19206) (루밀LuMir)
8a941cb docs: update docs and description of require-unicode-regexp (#19205) (루밀LuMir)
cbab228 docs: Update README (GitHub Actions Bot)
f2257ce docs: update comments and description of no-script-url (#19203) (루밀LuMir)
365f0f4 docs: add missing backtick to default-case-last (#19202) (루밀LuMir)
e6b84f5 docs: add missing punctuation in document (#19161) (루밀LuMir)
c88708e docs: replace quote with backtick in description of for-direction (#19199) (루밀LuMir)
a76f233 docs: use higher contrast color tokens for code comments (#19187) (Josh Goldberg ✨)
db19502 docs: Update README (GitHub Actions Bot)

Chores

cc243c9 chore: upgrade to @eslint/[email protected] (#19242) (Francesco Trotta)
84c5787 chore: package.json update for @eslint/js release (Jenkins)
4c4f53b chore: add missing backticks to flags.js (#19226) (루밀LuMir)
4b3132c chore: update dependency eslint-plugin-expect-type to ^0.6.0 (#19221) (renovate[bot])
9bf2204 chore: add type definitions for the eslint-config-eslint package (#19050) (Arya Emami)
ee8c220 chore: fix incorrect name property in integration-tutorial-code (#19218) (루밀LuMir)
cca801d chore: Upgrade cross-spawn to 7.0.6 (#19185) (folortin)

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v8.19.0`

Compare Source

🚀 Features

eslint-plugin: [strict-boolean-expressions] check array predicate functions' return statements (#10106)

🩹 Fixes

eslint-plugin: [member-ordering] ignore method overloading (#10536)
eslint-plugin: [consistent-indexed-object-style] don't report on indirect circular references (#10537)
eslint-plugin: [array-type] autofix with conditional types needs parentheses (#10522)
eslint-plugin: add getConstraintInfo to handle generic constraints better (#10496)

❤️ Thank You

Karl Werner
Kirk Waiblinger @kirkwaiblinger
Ronen Amiel
YeonJuan @yeonjuan

You can read about our versioning strategy and releases on our website.

`v8.18.2`

Compare Source

🩹 Fixes

eslint-plugin: [no-unnecessary-condition] handle noUncheckedIndexedAccess true (#10514)
eslint-plugin: [consistent-type-assertions] allow default assertionStyle option (#10512)
eslint-plugin: [no-unnecessary-type-arguments] handle type/value context (#10503)
eslint-plugin: [no-unsafe-type-assertion] fix for unsafe assertion to a constrained type parameter (#10461)
eslint-plugin: [consistent-indexed-object-style] use a suggestion over an auto-fix if can't reliably determine that produced index signature is valid (#10490)
eslint-plugin: [no-unnecessary-condition] don't flag values of an unconstrained or valid type parameter (#10473)
eslint-plugin: [prefer-reduce-type-parameter] don't report cases in which the fix results in a type error (#10494)
eslint-plugin: [no-deprecated] not reporting usages of deprecated declared constants as object value (#10498)

❤️ Thank You

Luke Deen Taylor @controversial
Ronen Amiel
Scott O'Hara
YeonJuan @yeonjuan
Yukihiro Hasegawa @y-hsgw

You can read about our versioning strategy and releases on our website.

`v8.18.1`

Compare Source

🩹 Fixes

scope-manager: visit params decorator before nest scope (#10475)
eslint-plugin: [no-unnecessary-condition] better message when comparing between literal types (#10454)
eslint-plugin: use consistent naming for asserting types and casting values (#10472)
eslint-plugin: [no-unnecessary-boolean-literal-compare] flag values of a type parameter with boolean type constraints (#10474)
eslint-plugin: handle string like index type (#10460)
eslint-plugin: [no-unnecessary-template-expression] don't report when an expression includes comment (#10444)

❤️ Thank You

Kirk Waiblinger @kirkwaiblinger
Ronen Amiel
YeonJuan @yeonjuan

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v8.19.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.

`v8.18.2`

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.

`v8.18.1`

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.

vitest-dev/vitest (@vitest/coverage-v8)

`v2.1.8`

Compare Source

🐞 Bug Fixes

Support Node 21 - by @sheremet-va (92f7a)

View changes on GitHub

`v2.1.7`

Compare Source

🐞 Bug Fixes

Revert support for Vite 6 - by @sheremet-va (fbe5c)
- This introduced some breaking changes (https://github.com/vitest-dev/vitest/issues/6992). We will enable support at a later time. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

View changes on GitHub

chalk/chalk (chalk)

`v5.4.1`

Compare Source

Fix navigator not defined ReferenceError (#642) 4ebb62d

`v5.4.0`

Compare Source

Update CIRCLECI environments to return level 3 color support f838120

evanw/esbuild (esbuild)

`v0.24.2`

Compare Source

Fix regression with --define and import.meta (#4010, #4012, #4013)

The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

This fix was contributed by @sapphi-red.

`v0.24.1`

Compare Source

Allow es2024 as a target in tsconfig.json (#4004)

TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:
```
{
  "compilerOptions": {
    "target": "ES2024"
  }
}
```
As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

This fix was contributed by @billyjanitsch.
Allow automatic semicolon insertion after get/set

This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
```
class Foo {
  get
  *x() {}
  set
  *y() {}
}
```
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in --define and --pure (#4008)

The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:
```
// The following code now transforms to "return true;\n"
console.log(esbuild.transformSync(
  `return process.env['SOME-TEST-VAR']`,
  { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
))
```
Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.
Minify empty try/catch/finally blocks (#4003)

With this release, esbuild will now attempt to minify empty try blocks:
```
// Original code
try {} catch { foo() } finally { bar() }

// Old output (with --minify)
try{}catch{foo()}finally{bar()}

// New output (with --minify)
bar();
```
This can sometimes expose additional minification opportunities.
Include entryPoint metadata for the copy loader (#3985)

Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.
Source mappings may now contain null entries (#3310, #3878)

With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.
Avoid using the parent directory name for determinism (#3998)

To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.
Experimental support for esbuild on NetBSD (#3974)

With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @bsiegert.

⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

eslint/eslint (eslint)

`v9.17.0`

Compare Source

un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

`v4.6.1`

Compare Source

Patch Changes

#211 be9c3e8 Thanks @mrginglymus! - Fix enhanced-resolve dependency

`v4.6.0`

Compare Source

Minor Changes

#209 46d2360 Thanks @SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue https://github.com/import-js/eslint-plugin-import/issues/1810.

So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #192.

In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

// eslint.config.js
const eslintPluginImportX = require('eslint-plugin-import-x');
const { createNodeResolver } = eslintPluginImportX;

module.exports = {
  plugins: {
    'import-x': eslintPluginImportX,
  },
  settings: {
    'import-x/resolver-next': [
      // This is the new resolver we are introducing
      createNodeResolver({
        /**
         * The allowed extensions the resolver will attempt to find when resolving a module
         * By default it uses a relaxed extension list to search for both ESM and CJS modules
         * You can customize this list to fit your needs
         *
         * @&#8203;default ['.mjs', '.cjs', '.js', '.json', '.node']
         */
        extensions?: string[];
        /**
         * Optional, the import conditions the resolver will used when reading the exports map from "package.json"
         * By default it uses a relaxed condition list to search for both ESM and CJS modules
         * You can customize this list to fit your needs
         *
         * @&#8203;default ['default', 'module', 'import', 'require']
         */
        conditions: ['default', 'module', 'import', 'require'],
        // You can pass more options here, see the enhanced-resolve documentation for more details
        // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options
      }),
      // you can add more resolvers down below
      require('eslint-import-resolver-typescript').createTypeScriptImportResolver(
        /** options of eslint-import-resolver-typescript */
      )
    ],
  },
};

We do not plan to implement reading baseUrl and paths from the tsconfig.json file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered by enhanced-resolve), eslint-import-resolver-oxc (powered by oxc-resolver), eslint-import-resolver-next (also powered by oxc-resolver), or other similar resolvers.

Patch Changes

#206 449738f Thanks @privatenumber! - insert type prefix without new line

`v4.5.1`

Compare Source

Patch Changes

#198 ac6d2e1 Thanks @voxpelli! - Fix #197 with missing types
#204 32e9b55 Thanks @privatenumber! - fix type-import and value-import merging when import-as is used

pnpm/pnpm (pnpm)

`v9.15.2`: pnpm 9.15.2

Compare Source

Patch Changes

Fixed publish/pack error with workspace dependencies with relative paths #8904. It was broken in v9.4.0 (398472c).
Use double quotes in the command suggestion by pnpm patch on Windows #7546.
Do not fall back to SSH, when resolving a git-hosted package if git ls-remote works via HTTPS #8906.
Improve how packages with blocked lifecycle scripts are reported during installation. Always print the list of ignored scripts at the end of the output. Include a hint about how to allow the execution of those packages.

Platinum Sponsors

Gold Sponsors

`v9.15.1`

Compare Source

`v9.15.0`

Compare Source

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.

<!-- 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>;

typescript-eslint/typescript-eslint (typescript-eslint)

`v8.19.0`

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

`v8.18.2`

Compare Source

🩹 Fixes

typescript-eslint: export types so that declarations can be named for dts files (#10513)

❤️ Thank You

Brad Zacher @bradzacher

You can read about our versioning strategy and releases on our website.

`v8.18.1`

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" in timezone Pacific/Auckland, 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.

codecov-commenter · 2024-12-31T11:31:43Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.75%. Comparing base (2c4163e) to head (18c9962).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #268   +/-   ##
=======================================
  Coverage   96.75%   96.75%           
=======================================
  Files           6        6           
  Lines         555      555           
  Branches      111      111           
=======================================
  Hits          537      537           
  Misses         17       17           
  Partials        1        1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

chore(deps): update all non-major dependencies

18c9962

renovate bot added the dependencies Pull requests that update a dependency file label Dec 31, 2024

renovate bot merged commit 64c7a7d into main Dec 31, 2024
6 checks passed

renovate bot deleted the renovate/all-minor-patch branch December 31, 2024 13:00

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

chore(deps): update all non-major dependencies #268

chore(deps): update all non-major dependencies #268

Uh oh!

renovate bot commented Dec 31, 2024

Uh oh!

codecov-commenter commented Dec 31, 2024

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

chore(deps): update all non-major dependencies #268

chore(deps): update all non-major dependencies #268

Uh oh!

Conversation

renovate bot commented Dec 31, 2024

Release Notes

Features

Bug Fixes

Documentation

Chores

🚀 Features

🩹 Fixes

❤️ Thank You

🩹 Fixes

❤️ Thank You

🩹 Fixes

❤️ Thank You

🐞 Bug Fixes

🐞 Bug Fixes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

v9.15.2: pnpm 9.15.2

Patch Changes

Platinum Sponsors

Gold Sponsors

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Fix comments print on class methods with decorators (#​16891 by @​fisker)

Fix non-idempotent formatting (#​16899 by @​seiyab)

🩹 Fixes

❤️ Thank You

Configuration

Uh oh!

codecov-commenter commented Dec 31, 2024

Codecov Report

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

`v9.15.2`: pnpm 9.15.2

Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)

Fix comments print on class methods with decorators (#16891 by @fisker)

Fix non-idempotent formatting (#16899 by @seiyab)