chore(deps): lock file maintenance npm packages #10137
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.26.8
->7.27.0
5.24.4
->5.24.5
1.3.1
->1.4.0
10.6.5
->10.7.0
19.0.0
->19.1.0
19.0.0
->19.1.0
4.0.0
->4.0.1
22.13.11
->22.13.14
0.25.1
->0.25.2
3.3.0
->3.3.1
0.16.2
->0.16.3
🔧 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
babel-generator
,babel-parser
importAttributesKeyword
towith
(@JLHwung)🚀 New Feature
babel-helper-create-class-features-plugin
,babel-traverse
,babel-types
traverseFast
to exit early (@liuxingbaoyu)babel-parser
,babel-types
ImportAttributes
toStandardized
and move its parser test fixtures (@JLHwung)babel-generator
babel-parser
,babel-template
allowYieldOutsideFunction
to parser (@liuxingbaoyu)babel-plugin-transform-typescript
,babel-traverse
upToScope
parameter tohasBinding
(@liuxingbaoyu)babel-parser
babel-types
🐛 Bug Fix
babel-helper-create-class-features-plugin
,babel-plugin-transform-class-properties
babel-traverse
scope.crawl()
(@liuxingbaoyu)babel-helpers
,babel-preset-typescript
,babel-runtime-corejs2
,babel-runtime-corejs3
,babel-runtime
rewriteRelativeImportExtensions
(@JLHwung)babel-cli
@babel/cli
generates duplicate inline source maps (@liuxingbaoyu)babel-plugin-transform-named-capturing-groups-regex
,babel-types
🏃♀️ Performance
babel-types
@babel/types
(@liuxingbaoyu)babel-helper-create-regexp-features-plugin
ant-design/ant-design (antd)
v5.24.5
Compare Source
resize: both
style to fit with React life cycle. #53235 @zombieJsuffix
出现左移的问题。#53184 @yellowryanresize: both
时处理尺寸的逻辑以更符合 React 生命周期。#53235 @zombieJtoyobayashi/emnapi (emnapi)
v1.4.0
Compare Source
What's Changed
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
andlist
also show settings set inpnpm-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:
The above configuration would apply
patches/foo-3.patch
tofoo@2.1.0
,patches/foo-2.patch
to allfoo
versions which satisfy^2.0.0
except2.1.0
, andpatches/foo-1.patch
to the remainingfoo
versions.pnpm config set --location=project
saves the setting to apnpm-workspace.yaml
file if no.npmrc
file is present in the directory #9316.Rename
pnpm.allowNonAppliedPatches
topnpm.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 tofalse
, pnpm would throw an error when any type of patch fails to apply.If
ignorePatchFailures
is explicitly set totrue
, pnpm would print a warning when any type of patch fails to apply.Patch Changes
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 theflags
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 thei
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 = ...
ormodule.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 fileexport let foo, bar
from ESM to CommonJS, esbuild appends this to the end of the file: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:
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:
This list of changes was auto generated.
oxc-project/oxc (oxlint)
v0.16.3
: oxlint v0.16.3Compare Source
[0.16.3] - 2025-03-25
Features
1b41cb3
linter: Add suggested fix tounicorn/prefer-structured-clone
(#9994) (Ulrich Stark 🦀)24cbe51
linter: Add suggested fixer totypescript/no_unnecessary_parameter_property_assignment
and fix false positive (#9973) (Ulrich Stark 🦀)Bug Fixes
6c4b533
linter: False positive inimport/no-empty-named-blocks
(#9974) (shulaoda)ff13be6
linter: Correct fixer for spread in function arguments (#9972) (shulaoda)Refactor
0f1e0e8
linter: Gate rule docs behind feature (#10027) (camchenry)ad06194
linter: Add fixer fortypescript-eslint/no-non-null-asserted-optional-chain
(#9993) (camchenry)402d8b7
linter: Improveeslint/no-redeclare
(#9976) (shulaoda)be62d38
rust: Remove usages oflazy_static
(#10007) (Boshen)6432707
rust: Uselazy-regex
(#10004) (Boshen)0fa58d7
semantic: Always useSymbolFlags::Function
for function id (#7479) (Dunqing)Testing
878bec6
editor: Add test foroxc.toggleEnable
command (#9987) (Sysix)093e7e5
editor: Addoxc.showOutputChannel
command test (#9986) (Sysix)c3af9a4
editor: Add tests for listing all oxc commands (#9930) (Sysix)71dce1f
editor: Add end-to-end tests for linter output (#9979) (Cam McHenry)c2f1be0
editor: Add tests foroffset_to_position
(#9978) (camchenry)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.
This PR was generated by Mend Renovate. View the repository job log.