This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	^22.13.13 -> ^22.13.14
@types/node (source)	^20.17.27 -> ^20.17.28
@vite-pwa/vitepress	^0.5.3 -> ^0.5.4
@wdio/protocols (source)	^9.7.0 -> ^9.12.2
@wdio/types (source)	^9.10.1 -> ^9.12.2
esbuild	^0.25.1 -> ^0.25.2
expect-type	^1.2.0 -> ^1.2.1
immutable (source)	5.0.3 -> 5.1.1
pnpm (source)	10.6.5 -> 10.7.0
react (source)	^19.0.0 -> ^19.1.0
react-dom (source)	^19.0.0 -> ^19.1.0
react-is (source)	^19.0.0 -> ^19.1.0
rollup (source)	^4.37.0 -> ^4.38.0
vite-plugin-pages	^0.32.5 -> ^0.33.0
webdriverio (source)	^9.12.1 -> ^9.12.2

---

Release Notes

vite-pwa/vitepress (@​vite-pwa/vitepress)

v0.5.4

Compare Source

   🚀 Features

• Update vite-plugin-pwa to 0.21.2  -  by @​userquin in https://github.com/vite-pwa/vitepress/issues/41 (5f5df)

    View changes on GitHub

webdriverio/webdriverio (@​wdio/protocols)

v9.12.2

Compare Source

🚀 New Feature

• webdriver
  • #​14304 feat(webdriver): support WebSocket options at the BiDi connection (@​mato533)

🐛 Bug Fix

• webdriver
  • #​14336 fix(webdriverio): try/catch dns lookup (@​christian-bromann)
• webdriverio
  • #​14321 fix: android deepLink using package instead of packageName (@​fabioatcorreia)
• wdio-utils
  • #​14311 Reduce wait port retry interval (@​dragosMC91)
• wdio-browserstack-service
  • #​14280 Bug Fix: missing Platform version on BrowserStack Observability (@​AdityaHirapara)

💅 Polish

• wdio-browserstack-service
  • #​14332 SDK-2064 A11y-Platform-Level-Support (@​xxshubhamxx)
  • #​14312 Percy binary update (@​sauravdas1997)

📝 Documentation

• Other
  • #​14335 fix: fix in docs formatter to accept new types (@​Rondleysg)
  • #​14329 fix(docs): resolving broken sauce connect proxy link (@​rbronz)
  • #​14318 docs: boilerplate project added to MD (@​Rondleysg)
  • #​14320 docs: update docker docs to use official puppeteer image (@​alcpereira)
  • #​14308 fix(docs): resolving broken github actions links (@​Sandi2212)
• wdio-cli, wdio-protocols, wdio-sauce-service, wdio-spec-reporter, wdio-types
  • #​14327 docs: fix all references to Sauce Labs docs (@​Rondleysg)
• wdio-spec-reporter
  • #​14306 updated spec reporter readme - sharable links value with valid sauce sharable link (@​vjuturu)

Committers: 13

• Aditya Hirapara (@​AdityaHirapara)
• Chanatan Charnkijtawarush (@​ccharnkij)
• Christian Bromann (@​christian-bromann)
• Dragos Campean (@​dragosMC91)
• Fábio Correia (@​fabioatcorreia)
• Rondley Gregório (@​Rondleysg)
• Shubham Garg (@​xxshubhamxx)
• @​Sandi2212
• @​alcpereira
• @​mato533
• @​rbronz
• @​sauravdas1997
• @​vjuturu

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.

mmkal/expect-type (expect-type)

v1.2.1

Compare Source

• docs: update deprecated usage examples 0c5a05d

---

immutable-js/immutable-js (immutable)

v5.1.1

Compare Source

What's Changed

Fix issue in builded types files in 5.1.0 due to cpy-cli upgrade

Full Changelog: immutable-js/immutable-js@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

• Add shuffle to list #​2066 by @​mazerty
• TypeScript: Better getIn RetrievePath #​2070 by @​jdeniau
• Fix #​1915 "Converting a Seq to a list causes RangeError (max call size exceeded)" by @​alexvictoor in #​2038
• TypeScript: Fix proper typings for Seq.concat() #​2040 by @​alexvictoor
• Fix Uncaught "TypeError: keyPath.slice is not a function" for ArrayLike method #​2065 by @​jdeniau

Internal

• Upgrade typescript and typescript-eslint #​2046 by @​jdeniau
• Upgrade to rollup 4 #​2049 by @​jdeniau
• Start migrating codebase to TypeScript without any runtime change nor .d.ts change:
  • allow TS files to be compiled in src dir #​2054 by @​jdeniau
• add exception for code that should not happen in updateIn #​2074 by @​jdeniau
• Reformat Range.toString for readability #​2075 by @​Ustin.Vaskin

New Contributors

• @​mazerty made their first contribution in https://github.com/immutable-js/immutable-js/pull/2066
• @​ustinvaskin made their first contribution in https://github.com/immutable-js/immutable-js/pull/2075

Full Changelog: immutable-js/immutable-js@v5.0.2...v5.1.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

facebook/react (react-is)

v19.1.0

Compare Source

Owner Stack

An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. You can log Owner Stacks when debugging or use Owner Stacks to enhance error overlays or other development tools. Owner Stacks are only available in development builds. Component Stacks in production are unchanged.

• An Owner Stack is a development-only stack trace that helps identify which components are responsible for rendering a particular component. An Owner Stack is distinct from a Component Stacks, which shows the hierarchy of components leading to an error.
• The captureOwnerStack API is only available in development mode and returns a Owner Stack, if available. The API can be used to enhance error overlays or log component relationships when debugging. #​29923, #​32353, #​30306,
  #​32538, #​32529, #​32538

React

• Enhanced support for Suspense boundaries to be used anywhere, including the client, server, and during hydration. #​32069, #​32163, #​32224, #​32252
• Reduced unnecessary client rendering through improved hydration scheduling #​31751
• Increased priority of client rendered Suspense boundaries #​31776
• Fixed frozen fallback states by rendering unfinished Suspense boundaries on the client. #​31620
• Reduced garbage collection pressure by improving Suspense boundary retries. #​31667
• Fixed erroneous “Waiting for Paint” log when the passive effect phase was not delayed #​31526
• Fixed a regression causing key warnings for flattened positional children in development mode. #​32117
• Updated useId to use valid CSS selectors, changing format from :r123: to «r123». #​32001
• Added a dev-only warning for null/undefined created in useEffect, useInsertionEffect, and useLayoutEffect. #​32355
• Fixed a bug where dev-only methods were exported in production builds. React.act is no longer available in production builds. #​32200
• Improved consistency across prod and dev to improve compatibility with Google Closure Complier and bindings #​31808
• Improve passive effect scheduling for consistent task yielding. #​31785
• Fixed asserts in React Native when passChildrenWhenCloningPersistedNodes is enabled for OffscreenComponent rendering. #​32528
• Fixed component name resolution for Portal #​32640
• Added support for beforetoggle and toggle events on the dialog element. #​32479 #​32479

React DOM

• Fixed double warning when the href attribute is an empty string #​31783
• Fixed an edge case where getHoistableRoot() didn’t work properly when the container was a Document #​32321
• Removed support for using HTML comments (e.g. <!-- -->) as a DOM container. #​32250
• Added support for <script> and <template> tags to be nested within <select> tags. #​31837
• Fixed responsive images to be preloaded as HTML instead of headers #​32445

use-sync-external-store

• Added exports field to package.json for use-sync-external-store to support various entrypoints. #​25231

React Server Components

• Added unstable_prerender, a new experimental API for prerendering React Server Components on the server #​31724
• Fixed an issue where streams would hang when receiving new chunks after a global error #​31840, #​31851
• Fixed an issue where pending chunks were counted twice. #​31833
• Added support for streaming in edge environments #​31852
• Added support for sending custom error names from a server so that they are available in the client for console replaying. #​32116
• Updated the server component wire format to remove IDs for hints and console.log because they have no return value #​31671
• Exposed registerServerReference in client builds to handle server references in different environments. #​32534
• Added react-server-dom-parcel package which integrates Server Components with the Parcel bundler #​31725, #​32132, #​31799, #​32294, #​31741

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])

hannoeru/vite-plugin-pages (vite-plugin-pages)

v0.33.0

Compare Source

   🚨 Breaking Changes

• Remove all deprecated options  -  by @​hannoeru (f3ea1)

   🐞 Bug Fixes

• Exclude option not work when file changed  -  by @​hannoeru (26428)
• Cjs import issue on utils  -  by @​hannoeru (6ac6b)
• deps: Update all non-major dependencies  -  in https://github.com/hannoeru/vite-plugin-pages/issues/659 (a5a88)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.