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

renovate · 2025-03-21T23:06:36Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@rspack/core (source)	`^1.2.8` -> `^1.3.0`
esbuild	`^0.25.1` -> `^0.25.2`
knip (source)	`^5.46.1` -> `^5.46.4`
nitropack	`^2.11.7` -> `^2.11.8`
pnpm (source)	`10.6.5` -> `10.7.0`
rollup (source)	`4.37.0` -> `4.38.0`
tinyexec	`^1.0.0` -> `^1.0.1`
typescript (source)	`^5.6.2` -> `^5.8.2`
typescript-eslint (source)	`^7.14.0` -> `^7.18.0`
undici (source)	`^7.5.0` -> `^7.6.0`
unimport	`4.1.2` -> `4.1.3`
vitest (source)	`^3.0.9` -> `^3.1.1`

Release Notes

web-infra-dev/rspack (@rspack/core)

`v1.3.0`

Compare Source

What's Changed

See Announcing Rspack 1.3 for more details.

Breaking Changes 🛠

feat(deps)!: update SWC version to 16.5.0 by @GiveMe-A-Name in https://github.com/web-infra-dev/rspack/pull/9671

Performance Improvements ⚡

perf: remove useless iterator in new code splitting and some allocations by @JSerFeng in https://github.com/web-infra-dev/rspack/pull/9821

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.

webpro-nl/knip (knip)

`v5.46.4`

Compare Source

`v5.46.3`

Compare Source

Add support for webpack.ProvidePlugin (resolves #840) (6a69543)
Add cache to pnpm commands (resolves #1010) (5f2efd4)
Don't reuse principals with rootDir set (resolves #1007) (7ba16e1)

`v5.46.2`

Compare Source

nitrojs/nitro (nitropack)

`v2.11.8`

Compare Source

compare changes

🩹 Fixes

dev: Conditionally set headers for error handler (#3249)
aws-lambda: Aws-lambda-streaming set-cookie headers (#3236)
config: Resolve srcDir relative to rootDir (#3250)

📦 Build

Inline openapi-typescript types to reduce install size by 39MB (#3252)

❤️ Contributors

Pooya Parsa (@pi0)
McKittrick Kaminski (@mckamyk)

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
  [email protected]: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to [email protected], 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
  '[email protected]': 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.

rollup/rollup (rollup)

`v4.38.0`

Compare Source

2025-03-29

Features

Support .filter option in resolveId, load and transform hooks (#5882)

Pull Requests

#5882: Add support for hook filters (@sapphi-red)
#5894: fix(deps): lock file maintenance minor/patch updates (@renovate[bot])
#5895: chore(deps): update dependency eslint-plugin-unicorn to v58 (@renovate[bot])

tinylibs/tinyexec (tinyexec)