Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 31, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/core (source) ^1.11.5 -> ^1.11.21 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^8.25.0 -> ^8.31.0 age adoption passing confidence
esbuild ^0.25.0 -> ^0.25.2 age adoption passing confidence
eslint (source) ^9.21.0 -> ^9.25.1 age adoption passing confidence
eslint-config-prettier ^10.0.2 -> ^10.1.2 age adoption passing confidence
eslint-import-resolver-typescript ^4.3.1 -> ^4.3.4 age adoption passing confidence
eslint-plugin-import-x ^4.6.1 -> ^4.10.6 age adoption passing confidence
pnpm (source) 10.5.2 -> 10.9.0 age adoption passing confidence
prettier (source) ^3.5.2 -> ^3.5.3 age adoption passing confidence
typescript (source) ^5.8.2 -> ^5.8.3 age adoption passing confidence
typescript-eslint (source) ^8.25.0 -> ^8.31.0 age adoption passing confidence

Release Notes

swc-project/swc (@​swc/core)

v1.11.21

Compare Source

Bug Fixes
Miscellaneous Tasks
Performance

v1.11.20

Compare Source

Bug Fixes

Related issue:

Features
Miscellaneous Tasks
Performance
Testing

v1.11.18

Compare Source

Bug Fixes
Features
Refactor
Testing

v1.11.16

Compare Source

Miscellaneous Tasks

v1.11.15

Compare Source

Bug Fixes
Documentation
Features
Miscellaneous Tasks
Performance
Refactor
Testing

v1.11.13

Compare Source

Features
Performance

v1.11.12

Compare Source

Bug Fixes
Documentation
Features
Performance
  • (es/minifier) Merge dead_branch_remover into pure optimizer (#​10201) (6841523)

v1.11.11

Compare Source

Bug Fixes
Features
Miscellaneous Tasks
Refactor
Testing

v1.11.10

Compare Source

Bug Fixes
  • (es/proposal) Fix declarations for explicit-resource-management (#​10198) (99ba555)

  • (es/types) Add missing types for jsc.transform.react.refresh (#​10206) (e71b000)

  • (typescript) Skip the body of ArrowExpr in type usage analysis (#​10187) (9aca205)

Documentation
Features
Miscellaneous Tasks
Performance
  • (es/minifier) Do not repeat applying pure minifier on last (#​10196) (e6b7cee)
Refactor
Testing

v1.11.9

Compare Source

Bug Fixes
  • (es/compat) Hoist arguments in object method while lowering async functions (#​10167) (e764df2)

  • (es/minifier) Check array inline for indexed with dynamic key (#​10184) (c2fe4bf)

Features
Performance

v1.11.8

Compare Source

Bug Fixes
Features
Performance
Refactor
Ci

v1.11.7

Compare Source

Features

v1.11.6

Compare Source

Bug Fixes
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.31.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unnecessary-type-assertion] add option to ignore string const assertions (#​10979)
❤️ Thank You
  • Nicolas Le Cam

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

v8.30.1

Compare Source

🩹 Fixes
  • eslint-plugin: fix mistake with eslintrc config generation (#​11072)
❤️ Thank You

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

v8.30.0

Compare Source

🚀 Features
  • eslint-plugin: [no-explicit-any] suggest to replace keyof any with PropertyKey (#​11032)
🩹 Fixes
  • eslint-plugin: [promise-function-async] use a different error message for functions with promise and non-promise types (#​10950)
❤️ Thank You

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

v8.29.1

Compare Source

🩹 Fixes
  • eslint-plugin: [no-deprecated] report on deprecated imported variable used as property (#​10998)
❤️ Thank You
  • Ronen Amiel

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

v8.29.0

Compare Source

🚀 Features
  • eslint-plugin: [prefer-nullish-coalescing] create ignoreIfStatements option (#​11000)
🩹 Fixes
  • eslint-plugin: [no-array-constructor] remove optional chaining exemption (#​10963)
  • eslint-plugin: support arbitrary extensions in definition files (#​10957)
  • eslint-plugin: [prefer-for-of] fix false positive when using erasable type syntax within update expressions (#​10981)
  • eslint-plugin: [use-unknown-in-catch-callback-variable] remove fixable property (#​10993)
  • eslint-plugin: [no-unnecessary-condition] don't report on unnecessary optional array index access when noUncheckedIndexedAccess is enabled (#​10961)
❤️ Thank You

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

v8.28.0

Compare Source

🚀 Features
  • eslint-plugin: [prefer-nullish-coalescing] support if statement assignment (??=) and fix several minor bugs (#​10861)
🩹 Fixes
  • eslint-plugin: [no-unsafe-function-type] remove fixable property (#​10986)
❤️ Thank You

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

v8.27.0

Compare Source

🚀 Features
  • utils: support DeprecatedInfo for rule.meta.deprecated (#​10932)
❤️ Thank You

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

v8.26.1

Compare Source

🩹 Fixes
  • eslint-plugin: [no-unsafe-return] handle recursive type (#​10883)
  • eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as eligible for nullish coalescing (#​10865)
❤️ Thank You

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

v8.26.0

Compare Source

🚀 Features
  • eslint-plugin: [unified-signatures] support ignoring overload signatures with different JSDoc comments (#​10781)
  • eslint-plugin: [explicit-module-boundary-types] add an option to ignore overload implementations (#​10889)
  • eslint-plugin: [no-unused-var] handle implicit exports in declaration files (#​10714)
  • support TypeScript 5.8 (#​10903)
  • eslint-plugin: [no-unnecessary-type-parameters] special case tuples and parameter location arrays as single-use (#​9536)
🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-assertion] handle unknown (#​10875)
  • eslint-plugin: [no-invalid-void-type] report accessor properties with an invalid void type (#​10864)
  • eslint-plugin: [unified-signatures] does not differentiate truly private methods (#​10806)
❤️ Thank You

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

evanw/esbuild (esbuild)

v0.25.2

Compare Source

  • Support flags in regular expressions for the API (#​4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#​4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
    0 && (module.exports = {
      bar,
      foo
    });

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
    let foo
    export { foo as "foo!" }
    
    // Old output (with --format=cjs --platform=node)
    ...
    0 && (module.exports = {
      "foo!"
    });
    
    // New output (with --format=cjs --platform=node)
    ...
    0 && (module.exports = {
      "foo!": null
    });
  • Basic support for index source maps (#​3439, #​4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

Compare Source

  • Fix incorrect paths in inline source maps (#​4070, #​4075, #​4105)

    This fixes a regression from version 0.25.0 where esbuild didn't correctly resolve relative paths contained within source maps in inline sourceMappingURL data URLs. The paths were incorrectly being passed through as-is instead of being resolved relative to the source file containing the sourceMappingURL comment, which was due to the data URL not being a file URL. This regression has been fixed, and this case now has test coverage.

  • Fix invalid generated source maps (#​4080, #​4082, #​4104, #​4107)

    This release fixes a regression from version 0.24.1 that could cause esbuild to generate invalid source maps. Specifically under certain conditions, esbuild could generate a mapping with an out-of-bounds source index. It was introduced by code that attempted to improve esbuild's handling of "null" entries in source maps (i.e. mappings with a generated position but no original position). This regression has been fixed.

    This fix was contributed by @​jridgewell.

  • Fix a regression with non-file source map paths (#​4078)

    The format of paths in source maps that aren't i


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Mar 31, 2025
Copy link

coderabbitai bot commented Mar 31, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 6d8c9aa to 2ef5922 Compare April 7, 2025 05:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 344381b to 5424547 Compare April 14, 2025 19:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 55f0c15 to 694523b Compare April 21, 2025 14:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 694523b to 523ab9d Compare April 21, 2025 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants