Skip to content
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.

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

chore(deps): update frontend dependencies (major) #1259

Closed
wants to merge 1 commit into from

Conversation

ggrossetie
Copy link
Collaborator

@ggrossetie ggrossetie commented Feb 12, 2025

This PR contains the following updates:

Package Type Update Change
@sentry/react (source) dependencies major ^8.38.0 -> ^9.0.0
@welldone-software/why-did-you-render devDependencies major ~8.0 -> ~10.0.0
biblatex-csl-converter dependencies major ^1.11.0 -> ^3.0.0
clsx dependencies major ^1.2.1 -> ^2.0.0
downshift (source) dependencies major ^6.1.12 -> ^9.0.0
eslint (source) devDependencies major ^8.2.0 -> ^9.0.0
i18next (source) dependencies major ^22.4.15 -> ^24.0.0
i18next-browser-languagedetector dependencies major ^7.0.1 -> ^8.0.0
npm (source) volta major 10.9.2 -> 11.1.0
prettier (source) devDependencies major ^2.3.0 -> ^3.0.0
react (source) dependencies major ~18.3 -> ~19.0.0
react-dom (source) dependencies major ~18.3 -> ~19.0.0
react-i18next dependencies major ^12.2.2 -> ^15.0.0
react-redux dependencies major ^7.2.4 -> ^9.0.0
react-router-dom (source) dependencies major ^5.2.0 -> ^7.0.0
redux (source) dependencies major ^4.1.0 -> ^5.0.0
y-websocket dependencies major ^1.5.0 -> ^2.0.0

Release Notes

getsentry/sentry-javascript (@​sentry/react)

v9.2.0

Compare Source

Important Changes

This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.

  • feat(sveltekit): Add Support for Cloudflare (#​14672)

This release adds support for deploying SvelteKit applications to Cloudflare Pages.
A docs update with updated instructions will follow shortly.
Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.

Thank you @​SG60 for contributing this feature!

Other Changes
  • feat(core): Add addLink(s) to Sentry span (#​15452)
  • feat(core): Add links to span options (#​15453)
  • feat(deps): Bump @​sentry/webpack-plugin from 2.22.7 to 3.1.2 (#​15328)
  • feat(feedback): Disable Feedback submit & cancel buttons while submitting (#​15408)
  • feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#​15418)
  • feat(nuxt): Add enableNitroErrorHandler to server options (#​15444)
  • feat(opentelemetry): Add addLink(s) to span (#​15387)
  • feat(opentelemetry): Add links to span options (#​15403)
  • feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#​14916)
  • fix(browser): Ensure that performance.measure spans have a positive duration (#​15415)
  • fix(bun): Includes correct sdk metadata (#​15459)
  • fix(core): Add Google gmo error to Inbound Filters (#​15432)
  • fix(core): Ensure http.client span descriptions don't contain query params or fragments (#​15404)
  • fix(core): Filter out unactionable Facebook Mobile browser error (#​15430)
  • fix(nestjs): Pin dependency on @opentelemetry/instrumentation (#​15419)
  • fix(nuxt): Only use filename with file extension from command (#​15445)
  • fix(nuxt): Use SentryNuxtServerOptions type for server init (#​15441)
  • fix(sveltekit): Avoid loading vite config to determine source maps setting (#​15440)
  • ref(profiling-node): Bump chunk interval to 60s (#​15361)

Work in this release was contributed by @​6farer, @​dgavranic and @​SG60. Thank you for your contributions!

v9.1.0

Compare Source

Work in this release was contributed by @​Zen-cronic and @​filips-alpe. Thank you for your contribution!

v9.0.1

Compare Source

  • ref(flags): rename unleash integration param (#​15343)

v9.0.0

Compare Source

Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9.
Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/

A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes
  • doc(deno)!: Make Deno v2 the minimum supported version (#​15085)
  • feat!: Bump typescript to ~5.0.0 (#​14758)
  • feat!: Drop nitro-utils package (#​14998)
  • feat!: Only collect ip addresses with sendDefaultPii: true (#​15084)
  • feat!: Remove autoSessionTracking option (#​14802)
  • feat!: Remove enableTracing (#​15078)
  • feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#​15122)
  • feat!: Remove spanId from propagation context (#​14733)
  • feat!: Remove deprecated and unused code (#​15077)
  • feat!: Remove metrics API from the JS SDK (#​14745)
  • feat!: Require Node >=18 as minimum supported version (#​14749)
  • feat(astro)!: Respect user-specified source map setting (#​14941)
  • feat(browser)!: Remove captureUserFeedback method (#​14820)
  • feat(build)!: Drop pre-ES2020 polyfills (#​14882)
  • feat(core)!: Add normalizedRequest to samplingContext (#​14902)
  • feat(core)!: Always use session from isolation scope (#​14860)
  • feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#​14831)
  • feat(core)!: Remove BAGGAGE_HEADER_NAME export (#​14785)
  • feat(core)!: Remove TransactionNamingScheme type (#​14865)
  • feat(core)!: Remove addOpenTelemetryInstrumentation method (#​14792)
  • feat(core)!: Remove arrayify method (#​14782)
  • feat(core)!: Remove debugIntegration and sessionTimingIntegration (#​14747)
  • feat(core)!: Remove flatten method (#​14784)
  • feat(core)!: Remove getDomElement method (#​14797)
  • feat(core)!: Remove makeFifoCache method (#​14786)
  • feat(core)!: Remove memoBuilder export & WeakSet fallback (#​14859)
  • feat(core)!: Remove transactionContext from samplingContext (#​14904)
  • feat(core)!: Remove urlEncode method (#​14783)
  • feat(core)!: Remove deprecated Request type (#​14858)
  • feat(core)!: Remove deprecated request data methods (#​14896)
  • feat(core)!: Remove standalone Client interface & deprecate BaseClient (#​14800)
  • feat(core)!: Remove validSeverityLevels export (#​14765)
  • feat(core)!: Stop accepting event as argument for recordDroppedEvent (#​14999)
  • feat(core)!: Stop setting user in requestDataIntegration (#​14898)
  • feat(core)!: Type sdkProcessingMetadata more strictly (#​14855)
  • feat(core)!: Update hasTracingEnabled to consider empty trace config (#​14857)
  • feat(core)!: Update requestDataIntegration handling (#​14806)
  • feat(deno)!: Remove deno prepack (#​14829)
  • feat(ember)!: Officially drop support for ember <=3.x (#​15032)
  • feat(nestjs)!: Move nestIntegration into nest sdk and remove setupNestErrorHandler (#​14751)
  • feat(nestjs)!: Remove @WithSentry decorator (#​14762)
  • feat(nestjs)!: Remove SentryService (#​14759)
  • feat(nextjs)!: Don't rely on Next.js Build ID for release names (#​14939)
  • feat(nextjs)!: Remove experimental_captureRequestError (#​14607)
  • feat(nextjs)!: Respect user-provided source map generation settings (#​14956)
  • feat(node)!: Add support for Prisma v6 and drop v5 support (#​15120)
  • feat(node)!: Avoid http spans by default for custom OTEL setups (#​14678)
  • feat(node)!: Collect request sessions via HTTP instrumentation (#​14658)
  • feat(node)!: Remove processThreadBreadcrumbIntegration (#​14666)
  • feat(node)!: Remove fine grained registerEsmLoaderHooks (#​15002)
  • feat(opentelemetry)!: Exclusively pass root spans through sampling pipeline (#​14951)
  • feat(pinia)!: Include state of all stores in breadcrumb (#​15312)
  • feat(react)!: Raise minimum supported TanStack Router version to 1.63.0 (#​15030)
  • feat(react)!: Remove deprecated getNumberOfUrlSegments method (#​14744)
  • feat(react)!: Remove deprecated react router methods (#​14743)
  • feat(react)!: Update ErrorBoundary componentStack type (#​14742)
  • feat(remix)!: Drop support for Remix v1 (#​14988)
  • feat(remix)!: Remove autoInstrumentRemix option (#​15074)
  • feat(solidstart)!: Default to --import setup and add autoInjectServerSentry (#​14862)
  • feat(solidstart)!: No longer export sentrySolidStartVite (#​15143)
  • feat(solidstart)!: Respect user-provided source map setting (#​14979)
  • feat(svelte)!: Disable component update tracking by default (#​15265)
  • feat(sveltekit)!: Drop support for SvelteKit @​1.x (#​15037)
  • feat(sveltekit)!: Remove fetchProxyScriptNonce option (#​15123)
  • feat(sveltekit)!: Respect user-provided source map generation settings (#​14886)
  • feat(utils)!: Remove @sentry/utils package (#​14830)
  • feat(vue)!: Remove configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#​14856)
  • feat(vue/nuxt)!: No longer create "update" spans for component tracking by default (#​14602)
  • fix(node)!: Fix name of vercelAIIntegration to VercelAI (#​15298)
  • fix(vue)!: Remove logError from vueIntegration (#​14958)
  • ref!: Don't polyfill optional chaining and nullish coalescing (#​14603)
  • ref(core)!: Cleanup internal types, including ReportDialogOptions (#​14861)
  • ref(core)!: Mark exceptions from captureConsoleIntegration as handled: true by default (#​14734)
  • ref(core)!: Move shutdownTimeout option type from core to node (#​15217)
  • ref(core)!: Remove Scope type interface in favor of using Scope class (#​14721)
  • ref(core)!: Remove backwards compatible SentryCarrier type (#​14697)
Other Changes

Work in this release was contributed by @​aloisklink, @​arturovt, @​aryanvdesh, @​benjick, @​chris-basebone, @​davidturissini, @​GrizliK1988, @​jahands, @​jrandolf, @​kunal-511, @​maximepvrt, @​maxmaxme, @​mstrokin, @​nathankleyn, @​nwalters512, @​tannerlinsley, @​tjhiggins, and @​Zen-cronic. Thank you for your contributions!

welldone-software/why-did-you-render (@​welldone-software/why-did-you-render)

v10.0.1

Compare Source

  • notifier was not exposing ownerDataMap despite the documentation saying it should.

v10.0.0: Why Did You Render v10 Supporting React 19! 🎉🍾

Compare Source

¯\(ツ)/¯ The version was bumped from v8 to v10 directly and 10.0.0 is actually the same as the next 10.0.1. Sorry, I had some npm publishing issues ¯\(ツ)

[!NOTE]
I've joined the React team, specifically working on React tooling. This role has opened up exciting opportunities to enhance the developer experience for React users— and your input could offer valuable insights to help me with this effort. Please join the conversation in the discussion thread!

Breaking Changes

[!CAUTION]
The library was not tested with React Compiler at all. I believe it's completely incompatible with it.

[!CAUTION]
Not all re-renders are "bad". Sometimes shenanigan to reduce re-renders can either hurt your App's performance or have a neglagable effect, in which case it would be just a waste of your efforts, and complicate your code. Try to focus on heavier components when optimizing and use the React DevTools Profiler to measure the effects of any changes.

New Features
Internal
fiduswriter/biblatex-csl-converter (biblatex-csl-converter)

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.1.0

Compare Source

v2.0.4

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

lukeed/clsx (clsx)

v2.1.1

Compare Source

Patches

Chores

  • Add licenses.dev badge: 684509c
    This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

v2.1.0

Compare Source

Features

  • Add new clsx/lite submodule for string-only usage: 1a49142

    This is a 140b version of clsx that is ideal for Tailwind and/or React contexts, which typically follow this clsx usage pattern:

    clsx('foo bar', props.maybe && 'conditional classes', props.className);

    Important: This clsx/lite module ignores all non-string arguments and is therefore not a 1:1 replacement for clsx itself!

    import { clsx } from 'clsx';
    import { clsx as lite } from 'clsx/lite';
    
    // strings-only usage is identical
    clsx('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"
    lite('foo', null, 'bar', true && 'baz'); //=> "foo bar baz"
    
    // clsx/lite ignores all non-strings
    clsx('foo', { a: true, b: false, c: true }); //=> "foo a c"
    lite('foo', { a: true, b: false, c: true }); //=> "foo"

Full Changelog: lukeed/clsx@v2.0.1...v2.1.0

v2.0.1

Compare Source

Patches

  • (perf) Cache arguments.length & array.length for 6% performance gain (#​26): deff09b
    Adds 5 bytes (+2%) for ~3% avg performance gain
    Thank you @​jalalazimi

Chores


Full Changelog: lukeed/clsx@v2.0.0...v2.0.1

v2.0.0

Compare Source

Breaking

  • Add "exports" map for native ESM support (#​57): 3ec8e9f, 0949868
    Also supports TypeScript's node16/nodenext module resolution
    Maintains CommonJS support (with fixed TS definitions)
    Thank you @​remcohaszing~!

Chores


Full Changelog: lukeed/clsx@v1.2.1...v2.0.0

downshift-js/downshift (downshift)

v9.0.8

Compare Source

Bug Fixes

v9.0.7

Compare Source

Bug Fixes

v9.0.6

Compare Source

Bug Fixes

v9.0.5

Compare Source

Bug Fixes

v9.0.4

Compare Source

Bug Fixes

v9.0.3

Compare Source

Bug Fixes

v9.0.2

Compare Source

Bug Fixes

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Features
BREAKING CHANGES
  • Release Downshift v9.

Why:
Release the changes in:

Closes https://github.com/downshift-js/downshift/issues/1322.
Closes https://github.com/downshift-js/downshift/issues/1244.
Closes https://github.com/downshift-js/downshift/issues/1227
Closes https://github.com/downshift-js/downshift/issues/1225.

How:
Merged the PRs in this branch.

Checklist:

  • Documentation
  • Tests
  • TypeScript Types
  • Flow Types
  • Ready to be merged

v8.5.0

Compare Source

Features

v8.4.0

Compare Source

Features

v8.3.3

Compare Source

Bug Fixes
  • fixes issue causing combobox to grab focus on render (#​1575) (59366d9)

v8.3.2

Compare Source

Bug Fixes

v8.3.1

Compare Source

Bug Fixes

v8.3.0

Compare Source

Features

v8.2.4

Compare Source

Bug Fixes

v8.2.3

Compare Source

Bug Fixes

v8.2.2

Compare Source

Bug Fixes
  • typescript: add onPress to toggle button props parameter (#​1548) (fd6ab68)

v8.2.1

Compare Source

Bug Fixes
  • defaultProps: use undefined environment on React Native (#​1546) (7d8c32d)
  • useSelect: preventDefault on item props onMouseDown (b24f2e6)
  • useSelect: preventDefault on item props onMouseDown (#​1547) (05ffa9c)

v8.2.0

Compare Source

Features

v8.1.1

Compare Source

Bug Fixes
  • typescript: missing generic parameter of React.RefObject (#​1536) (bc7639c)

v8.1.0

Compare Source

Features

[v8.0.2](https:


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 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 has been generated by Renovate Bot.

@ggrossetie
Copy link
Collaborator Author

ggrossetie commented Feb 12, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: front/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @monaco-editor/react@4.6.0
npm error Found: react@19.0.0
npm error node_modules/react
npm error   react@"~19.0.0" from the root project
npm error   peer overridden react@"~19.0.0" (was ">=16.9.0") from @geist-ui/core@2.3.8
npm error   node_modules/@geist-ui/core
npm error     @geist-ui/core@"^2.3.8" from the root project
npm error   17 more (@rjsf/core, @rjsf/utils, @testing-library/react, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @monaco-editor/react@4.6.0
npm error node_modules/@monaco-editor/react
npm error   @monaco-editor/react@"~4.6" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @monaco-editor/react@4.6.0
npm error   node_modules/@monaco-editor/react
npm error     @monaco-editor/react@"~4.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-02-26T02_37_20_790Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-02-26T02_37_20_790Z-debug-0.log

Copy link

netlify bot commented Feb 12, 2025

Deploy Preview for stylo-docs canceled.

Name Link
🔨 Latest commit a3c140f
🔍 Latest deploy log https://app.netlify.com/sites/stylo-docs/deploys/67be7e67499cd40008746fad

@ggrossetie ggrossetie force-pushed the renovate/major-frontend-dependencies branch from 49ad5e8 to 942ca94 Compare February 14, 2025 02:37
@ggrossetie ggrossetie force-pushed the renovate/major-frontend-dependencies branch from 942ca94 to 8a12967 Compare February 21, 2025 02:37
@ggrossetie ggrossetie force-pushed the renovate/major-frontend-dependencies branch from 8a12967 to a3c140f Compare February 26, 2025 02:37
@ggrossetie ggrossetie closed this Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant