fix(deps): update minor and patch

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@qlik/api	^1.29.0 -> ^1.30.0
@testing-library/react	^16.2.0 -> ^16.3.0
caniuse-lite	1.0.30001707 -> 1.0.30001712
eslint-plugin-prettier	5.2.5 -> 5.2.6
eslint-plugin-react	7.37.4 -> 7.37.5
puppeteer (source)	24.4.0 -> 24.6.0
qlik-chart-modules	0.82.0 -> 0.85.0
react-router (source)	7.4.1 -> 7.5.0
rollup (source)	4.38.0 -> 4.39.0
typescript (source)	>=5.8.2 -> >=5.8.3
webpack	5.98.0 -> 5.99.2

---

Release Notes

qlik-oss/qlik-api-ts (@​qlik/api)

v1.30.0

Compare Source

What's Changed

• feat: add oauth-clients to qlik-api
• feat: add productId and version to platform meta
• fix: handle removed body/query
• fix: WS connection can be created twice
• feat: update from latest specs

Full Changelog: qlik-oss/qlik-api-ts@v1.29.0...v1.30.0

testing-library/react-testing-library (@​testing-library/react)

v16.3.0

Compare Source

browserslist/caniuse-lite (caniuse-lite)

v1.0.30001712

Compare Source

v1.0.30001711

Compare Source

v1.0.30001710

Compare Source

v1.0.30001709

Compare Source

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.6

Compare Source

Patch Changes

• #​723 1451176 Thanks @​renovate! - fix(deps): bump synckit to v0.11.0

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.37.5

Compare Source

Fixed

• [no-unknown-property]: allow shadow root attrs on <template> (#​3912 @​ljharb)
• [prop-types]: support ComponentPropsWithRef from a namespace import (#​3651 @​corydeppen)
• [jsx-no-constructed-context-values]: detect constructed context values in React 19 <Context> usage (#​3910 @​TildaDares)
• [no-unknown-property]: allow transform-origin on rect (#​3914 @​ljharb)

Changed

• [Docs] [button-has-type]: clean up phrasing (#​3909 @​hamirmahal)

puppeteer/puppeteer (puppeteer)

v24.6.0

Compare Source

Features

• roll to Chrome 135.0.7049.42 (#​13717) (30b7ba8)
• roll to Firefox 137.0 (#​13720) (bee835f)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • puppeteer-core bumped from 24.5.0 to 24.6.0

v24.5.0

Compare Source

Miscellaneous Chores

• puppeteer: Synchronize puppeteer versions

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​puppeteer/browsers bumped from 2.8.0 to 2.9.0

Features

• improve screencast options (#​13645) (22aeab9)

Bug Fixes

• screencast mp4 encoding (#​13676) (dfc9219)
• roll to Chrome 134.0.6998.165 (#​13696) (ff74c58)
• roll to Chrome 134.0.6998.88 (#​13666) (334d06a)
• roll to Chrome 134.0.6998.90 (#​13693) (7433674)
• roll to Firefox 136.0.1 (#​13672) (c900ded)
• roll to Firefox 136.0.2 (#​13692) (ea8a0ae)
• roll to Firefox 136.0.3 (#​13702) (d3a865e)
• roll to Firefox 136.0.4 (#​13707) (33668c9)

remix-run/react-router (react-router)

v7.5.0

Compare Source

Minor Changes

• Add granular object-based API for route.lazy to support lazy loading of individual route properties, for example: (#​13294)

  createBrowserRouter([
    {
      path: "/show/:showId",
      lazy: {
        loader: async () => (await import("./show.loader.js")).loader,
        action: async () => (await import("./show.action.js")).action,
        Component: async () => (await import("./show.component.js")).Component,
      },
    },
  ]);

  Breaking change for route.unstable_lazyMiddleware consumers

  The route.unstable_lazyMiddleware property is no longer supported. If you want to lazily load middleware, you must use the new object-based route.lazy API with route.lazy.unstable_middleware, for example:

  createBrowserRouter([
    {
      path: "/show/:showId",
      lazy: {
        unstable_middleware: async () =>
          (await import("./show.middleware.js")).middleware,
        // etc.
      },
    },
  ]);

Patch Changes

• Introduce unstable_subResourceIntegrity future flag that enables generation of an importmap with integrity for the scripts that will be loaded by the browser. (#​13163)

rollup/rollup (rollup)

v4.39.0

Compare Source

2025-04-02

Features

• Do not create separate facade chunks if a chunk would contain several entry modules that allow export extension if there are no export name conflicts (#​5891)

Bug Fixes

• Mark the id property as optional in the filter for the resolveId hook (#​5896)

Pull Requests

• #​5891: chunk: merge allow-extension modules (@​wmertens, @​lukastaegert)
• #​5893: chore(deps): update dependency vite to v6.2.4 [security] (@​renovate[bot])
• #​5896: fix: resolveId id filter is optional (@​sapphi-red)

microsoft/TypeScript (typescript)

v5.8.3

Compare Source

webpack/webpack (webpack)

v5.99.2

Compare Source

v5.99.1

Compare Source

Fixes

• Dead control flow for many cases

v5.99.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* * * * 0,6" (UTC), 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.