Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 30, 2025

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed
@babel/plugin-transform-typescript (source) dependencies minor 7.26.8 -> 7.27.0 age adoption passing confidence
antd (source) devDependencies patch 5.24.4 -> 5.24.5 age adoption passing confidence
emnapi devDependencies minor 1.3.1 -> 1.4.0 age adoption passing confidence
pnpm (source) packageManager minor 10.6.5 -> 10.7.0 age adoption passing confidence
react (source) devDependencies minor 19.0.0 -> 19.1.0 age adoption passing confidence
react-dom (source) devDependencies minor 19.0.0 -> 19.1.0 age adoption passing confidence
@codspeed/vitest-plugin (source) devDependencies patch 4.0.0 -> 4.0.1 age adoption passing confidence
@types/node (source) devDependencies patch 22.13.11 -> 22.13.14 age adoption passing confidence
esbuild devDependencies patch 0.25.1 -> 0.25.2 age adoption passing confidence
@vscode/vsce (source) devDependencies patch 3.3.0 -> 3.3.1 age adoption passing confidence
oxlint (source) devDependencies patch 0.16.2 -> 0.16.3 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.


Release Notes

babel/babel (@​babel/plugin-transform-typescript)

v7.27.0

Compare Source

👓 Spec Compliance
🚀 New Feature
🐛 Bug Fix
  • babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties
  • babel-traverse
  • babel-helpers, babel-preset-typescript, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-cli
  • babel-plugin-transform-named-capturing-groups-regex, babel-types
🏃‍♀️ Performance
ant-design/ant-design (antd)

v5.24.5

Compare Source


toyobayashi/emnapi (emnapi)

v1.4.0

Compare Source

What's Changed

  • allow napi_delete_reference in basic finalizers (#​130)
  • define NAPI_VERSION 10 (#​133)
  • perf: reduce the overhead of binding function call (1.5x faster) (#​139)
Note

If you are using Emscripten >= 3.1.60, please manually specify the link option -sEXPORTED_RUNTIME_METHODS=['emnapiInit'] (#​131) (https://github.com/emscripten-core/emscripten/issues/23057)

Full Changelog: toyobayashi/emnapi@v1.3.1...v1.4.0

pnpm/pnpm (pnpm)

v10.7.0

Compare Source

Minor Changes
  • pnpm config get and list also show settings set in pnpm-workspace.yaml files #​9316.

  • It should be possible to use env variables in pnpm-workspace.yaml setting names and value.

  • Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

    For example:

    patchedDependencies:
      foo: patches/foo-1.patch
      foo@^2.0.0: patches/foo-2.patch
      foo@2.1.0: patches/foo-3.patch

    The above configuration would apply patches/foo-3.patch to foo@2.1.0, patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.

    [!WARNING]
    The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:

    # pnpm-workspace.yaml
    patchedDependencies:
      # the specialized sub range
      'foo@2.2.0-2.8.0': patches/foo.2.2.0-2.8.0.patch
      # the more general patch, excluding the sub range above
      'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch

    In most cases, however, it's sufficient to just define an exact version to override the range.

  • pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #​9316.

  • Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.

  • Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

    If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

    If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

    If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes
  • Remove dependency paths from audit output to prevent out-of-memory errors #​9280.
facebook/react (react)

v19.1.0

Compare Source

facebook/react (react-dom)

v19.1.0

Compare Source

CodSpeedHQ/codspeed-node (@​codspeed/vitest-plugin)

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: CodSpeedHQ/codspeed-node@v4.0.0...v4.0.1

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.

Microsoft/vsce (@​vscode/vsce)

v3.3.1

Compare Source

Changes:

  • #​1124: Add 'copilot-tools' to languageModelTools contributions

This list of changes was auto generated.

oxc-project/oxc (oxlint)

v0.16.3: oxlint v0.16.3

Compare Source

[0.16.3] - 2025-03-25

Features
  • 1b41cb3 linter: Add suggested fix to unicorn/prefer-structured-clone (#​9994) (Ulrich Stark 🦀)
  • 24cbe51 linter: Add suggested fixer to typescript/no_unnecessary_parameter_property_assignment and fix false positive (#​9973) (Ulrich Stark 🦀)
Bug Fixes
  • 6c4b533 linter: False positive in import/no-empty-named-blocks (#​9974) (shulaoda)
  • ff13be6 linter: Correct fixer for spread in function arguments (#​9972) (shulaoda)
Refactor
Testing

Configuration

📅 Schedule: Branch creation - "before 8am on monday" in timezone Asia/Shanghai, 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.

Copy link
Contributor

graphite-app bot commented Mar 30, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@github-actions github-actions bot added the C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior label Mar 30, 2025
@renovate renovate bot merged commit 8539da7 into main Mar 30, 2025
18 checks passed
@renovate renovate bot deleted the renovate/npm-packages branch March 30, 2025 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants