Skip to content

chore(deps): update bump npm dependencies #884

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update bump npm dependencies #884

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2025 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@eslint/js (source) 9.39.1 -> 9.39.2 age confidence
@mui/icons-material (source) 7.3.5 -> 7.3.6 age confidence
@mui/material (source) 7.3.5 -> 7.3.6 age confidence
@uiw/codemirror-theme-material (source) 4.25.3 -> 4.25.4 age confidence
@uiw/react-codemirror (source) 4.25.3 -> 4.25.4 age confidence
@vitejs/plugin-react (source) 5.1.1 -> 5.1.2 age confidence
eslint (source) 9.39.1 -> 9.39.2 age confidence
prettier (source) 3.7.3 -> 3.7.4 age confidence
puppeteer (source) 24.31.0 -> 24.34.0 age confidence
react (source) 19.2.0 -> 19.2.3 age confidence
react-dom (source) 19.2.0 -> 19.2.3 age confidence
react-router (source) 7.9.6 -> 7.11.0 age confidence
react-router-dom (source) 7.9.6 -> 7.11.0 age confidence
react-virtuoso (source) 4.15.0 -> 4.17.0 age confidence
tss-react (source) 4.9.19 -> 4.9.20 age confidence
typescript-eslint (source) 8.48.0 -> 8.50.1 age confidence
vite (source) 7.2.4 -> 7.3.0 age confidence
vitest (source) 4.0.14 -> 4.0.16 age confidence

Release Notes

eslint/eslint (@​eslint/js)

v9.39.2

Compare Source

mui/material-ui (@​mui/icons-material)

v7.3.6

Compare Source

Dec 3, 2025

A big thanks to the 22 contributors who made this release possible.

@​mui/material@​7.3.6
@​mui/system@​7.3.6
@​mui/lab@​7.3.6
Docs
Core

All contributors of this release in alphabetical order: @​Ad1tya-007, @​akankshahu, @​albarv340, @​Aleksan4e3, @​brijeshb42, @​Copilot, @​Fanzzzd, @​Janpot, @​JCQuintas, @​kumarvishwajeettrivedi, @​mapache-salvaje, @​oliviertassinari, @​pcorpet, @​rifeplight, @​rithik56, @​rossdakin, @​sai6855, @​shamblonaut, @​siriwatknp, @​vrachuri28, @​xBlizZer, @​ZeeshanTamboli

uiwjs/react-codemirror (@​uiw/codemirror-theme-material)

v4.25.4

Compare Source

Buy me a coffee

Documentation v4.25.4: https://raw.githack.com/uiwjs/react-codemirror/c6e2bc9/index.html
Comparing Changes: uiwjs/react-codemirror@v4.25.3...v4.25.4

npm i @​uiw/react-codemirror@4.25.4
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v5.1.2

Compare Source

eslint/eslint (eslint)

v9.39.2

Compare Source

prettier/prettier (prettier)

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);
puppeteer/puppeteer (puppeteer)

v24.34.0

Compare Source

♻️ Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 24.33.1 to 24.34.0
🎉 Features
🛠️ Fixes

v24.33.1

Compare Source

♻️ Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 24.33.1 to 24.34.0
🎉 Features
🛠️ Fixes

v24.33.0

Compare Source

♻️ Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 24.32.1 to 24.33.0
🎉 Features
🛠️ Fixes

v24.32.1

Compare Source

♻️ Chores
  • puppeteer: Synchronize puppeteer versions
Dependencies
  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 24.32.0 to 24.32.1
🛠️ Fixes
  • assertion errors and wrong URL in puppeteer.connect(channel) (#​14486) (1095b46)
📄 Documentation

v24.32.0

Compare Source

🎉 Features
Dependencies
  • The following workspace dependencies were updated
🛠️ Fixes
facebook/react (react)

v19.2.3: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

v19.2.2: 19.2.2 (December 11th, 2025)

Compare Source

React Server Components

v19.2.1: 19.2.1 (December 3rd, 2025)

Compare Source

React Server Components
remix-run/react-router (react-router)

v7.11.0

Compare Source

Minor Changes
  • Stabilize <HydratedRouter onError>/<RouterProvider onError> (#​14546)
Patch Changes

  • add support for throwing redirect Response's at RSC render time (#​14596)

  • Support for throwing data() and Response from server component render phase. Response body is not serialized as async work is not allowed as error encoding phase. If you wish to transmit data to the boundary, throw data() instead. (#​14632)

  • Fix unstable_useTransitions prop on <Router> component to permit omission for backewards compatibility (#​14646)

  • routeRSCServerRequest replace fetchServer with serverResponse (#​14597)

  • [UNSTABLE] Add a new unstable_defaultShouldRevalidate flag to various APIs to allow opt-ing out of standard revalidation behaviors. (#​14542)

    If active routes include a shouldRevalidate function, then your value will be passed as defaultShouldRevalidate in those function so that the route always has the final revalidation determination.

    • <Form method="post" unstable_defaultShouldRevalidate={false}>
    • submit(data, { method: "post", unstable_defaultShouldRevalidate: false })
    • <fetcher.Form method="post" unstable_defaultShouldRevalidate={false}>
    • fetcher.submit(data, { method: "post", unstable_defaultShouldRevalidate: false })

    This is also available on non-submission APIs that may trigger revalidations due to changing search params:

    • <Link to="/" unstable_defaultShouldRevalidate={false}>
    • navigate("/?foo=bar", { unstable_defaultShouldRevalidate: false })
    • setSearchParams(params, { unstable_defaultShouldRevalidate: false })

  • Allow redirects to be returned from client side middleware (#​14598)

  • Handle dataStrategy implementations that return insufficient result sets by adding errors for routes without any available result (#​14627)

v7.10.1

Compare Source

Patch Changes
  • Update the useOptimistic stub we provide for React 18 users to use a stable setter function to avoid potential useEffect loops - specifically when using <Link viewTransition> (#​14628)

v7.10.0

Compare Source

Minor Changes

  • Stabilize fetcher.reset() (#​14545)

    • ⚠️ This is a breaking change if you have begun using fetcher.unstable_reset()

  • Stabilize the dataStrategy match.shouldRevalidateArgs/match.shouldCallHandler() APIs. (#​14592)

    • The match.shouldLoad API is now marked deprecated in favor of these more powerful alternatives

    • If you're using this API in a custom dataStrategy today, you can swap to the new API at your convenience:

      // Before
const matchesToLoad = matches.filter((m) => m.shouldLoad);

// After
const matchesToLoad = matches.filter((m) => m.shouldCallHandler());

    • match.shouldRevalidateArgs is the argument that will be passed to the route shouldRevaliate function

    • Combined with the parameter accepted by match.shouldCallHandler, you can define a custom revalidation behavior for your dataStrategy:

    const matchesToLoad = matches.filter((m) => {
  const defaultShouldRevalidate = customRevalidationBehavior(
    match.shouldRevalidateArgs,
  );
  return m.shouldCallHandler(defaultShouldRevalidate);
  // The argument here will override the internal `defaultShouldRevalidate` value
});
Patch Changes

  • Fix a Framework Mode bug where the defaultShouldRevalidate parameter to shouldRevalidate would not be correct after action returned a 4xx/5xx response (true when it should have been false) (#​14592)

    • If your shouldRevalidate function relied on that parameter, you may have seen unintended revalidations

  • Fix fetcher.submit failing with plain objects containing a tagName property (#​14534)

  • [UNSTABLE] Add unstable_pattern to the parameters for client side unstable_onError, refactor how it's called by RouterProvider to avoid potential strict mode issues (#​14573)

  • Add new unstable_useTransitions flag to routers to give users control over the usage of React.startTransition and React.useOptimistic. (#​14524)

    • Framework Mode + Data Mode:
      • <HydratedRouter unstable_transition>/<RouterProvider unstable_transition>
      • When left unset (current default behavior)
        • Router state updates are wrapped in React.startTransition
        • ⚠️ This can lead to buggy behaviors if you are wrapping your own navigations/fetchers in React.startTransition
        • You should set the flag to true if you run into this scenario to get the enhanced useOptimistic behavior (requires React 19)
      • When set to true
        • Router state updates remain wrapped in React.startTransition (as they are without the flag)
        • Link/Form navigations will be wrapped in React.startTransition
        • A subset of router state info will be surfaced to the UI during navigations via React.useOptimistic (i.e., useNavigation(), useFetchers(), etc.)
          • ⚠️ This is a React 19 API so you must also be React 19 to opt into this flag for Framework/Data Mode
      • When set to false
        • The router will not leverage React.startTransition or React.useOptimistic on any navigations or state changes
    • Declarative Mode
      • <BrowserRouter unstable_useTransitions>
      • When left unset
        • Router state updates are wrapped in React.startTransition
      • When set to true
        • Router state updates remain wrapped in React.startTransition (as they are without the flag)
        • Link/Form navigations will be wrapped in React.startTransition
      • When set to false
        • the router will not leverage React.startTransition on any navigations or state changes

  • Fix the promise returned from useNavigate in Framework/Data Mode so that it properly tracks the duration of popstate navigations (i.e., navigate(-1)) (#​14524)

  • Fix internal type error in useRoute types that surfaces when skipLibCheck is disabled (#​14577)

  • Preserve statusText on the ErrorResponse instance when throwing data() from a route handler (#​14555)

  • Optimize href() to avoid backtracking regex on splat (#​14329)

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

v7.11.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.11.0

v7.10.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.10.1

v7.10.0

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@7.10.0
petyosi/react-virtuoso (react-virtuoso)

v4.17.0

Compare Source

Minor Changes
  • 58b9703: Add minOverscanItemCount prop to ensure a minimum number of items are rendered before/after the viewport, useful for tall or collapsible items where pixel-based overscan is insufficient.

v4.16.1

Compare Source

Patch Changes
garronej/tss-react (tss-react)

v4.9.20

Compare Source

Full Changelog: garronej/tss-react@v4.9.19...v4.9.20

typescript-eslint/typescript-eslint (typescript-eslint)

v8.50.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.50.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.49.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.48.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

vitejs/vite (vite)

v7.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.7

Compare Source

v7.2.6

Compare Source

7.2.6 (2025-12-01)

vitest-dev/vitest (vitest)

v4.0.16

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    [

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 3, 2025
@renovate renovate bot requested a review from a team as a code owner December 3, 2025 19:45
@renovate renovate bot added the dependencies Pull requests that update a dependency file label Dec 3, 2025
@codecov
Copy link

codecov bot commented Dec 3, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.15%. Comparing base (12e298d) to head (7ceb05b).

Additional details and impacted files 
@@           Coverage Diff           @@
##           master     #884   +/-   ##
=======================================
  Coverage   79.15%   79.15%           
=======================================
  Files          56       56           
  Lines        2226     2226           
=======================================
  Hits         1762     1762           
  Misses        360      360           
  Partials      104      104

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/bump-dependencies-npm branch from a1a32b2 to 788d48b Compare December 4, 2025 06:23
@renovate renovate bot changed the title chore(deps): update dependency react-virtuoso to v4.16.1 chore(deps): update bump npm dependencies Dec 4, 2025
@renovate renovate bot force-pushed the renovate/bump-dependencies-npm branch 7 times, most recently from 3d283bc to 4745dd0 Compare December 11, 2025 20:04
@renovate renovate bot force-pushed the renovate/bump-dependencies-npm branch 6 times, most recently from f4c4af0 to b2dd9fc Compare December 20, 2025 16:31
@renovate renovate bot force-pushed the renovate/bump-dependencies-npm branch from b2dd9fc to 802b9cc Compare December 22, 2025 10:50
@renovate renovate bot force-pushed the renovate/bump-dependencies-npm branch from 802b9cc to 7ceb05b Compare December 25, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant