Update react dependencies (major) #302
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.7.0→^5.1.2^5.2.0→^7.0.1^9.16.0→^10.0.0Release Notes
vitejs/vite-plugin-react (@vitejs/plugin-react)
v5.1.2Compare Source
v5.1.1Compare Source
Update code to support newer
rolldown-vite(#976)rolldown-vitewill removeoptimizeDeps.rollupOptionsin favor ofoptimizeDeps.rolldownOptionssoon. This plugin now usesoptimizeDeps.rolldownOptionsto support newerrolldown-vite. Please updaterolldown-viteto the latest version if you are using an older version.v5.1.0Compare Source
Add
@vitejs/plugin-react/preamblevirtual module for SSR HMR (#890)SSR applications can now initialize HMR runtime by importing
@vitejs/plugin-react/preambleat the top of their client entry instead of manually callingtransformIndexHtml. This simplifies SSR setup for applications that don't use thetransformIndexHtmlAPI.Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#930)
Rolldown 1.0.0-beta.44+ removed the top-level
jsxoption in favor oftransform.jsx. This plugin now uses thetransform.jsxoption to support Rolldown 1.0.0-beta.44+.v5.0.4Compare Source
Perf: use native refresh wrapper plugin in rolldown-vite (#881)
v5.0.3Compare Source
HMR did not work for components imported with queries with rolldown-vite (#872)
Perf: simplify refresh wrapper generation (#835)
v5.0.2Compare Source
Skip transform hook completely in rolldown-vite in dev if possible (#783)
v5.0.1Compare Source
Set
optimizeDeps.rollupOptions.transform.jsxinstead ofoptimizeDeps.rollupOptions.jsxfor rolldown-vite (#735)optimizeDeps.rollupOptions.jsxis going to be deprecated in favor ofoptimizeDeps.rollupOptions.transform.jsx.Perf: skip
babel-plugin-react-compilerif code has no"use memo"when{ compilationMode: "annotation" }(#734)Respect tsconfig
jsxImportSource(#726)Fix
reactRefreshHostoption on rolldown-vite (#716)Fix
RefreshRuntimebeing injected twice for class components on rolldown-vite (#708)Skip
babel-plugin-react-compileron non client environment (689)v5.0.0Compare Source
facebook/react (eslint-plugin-react-hooks)
v7.0.1Compare Source
useEffectEventvalues as JSX props to guard against accidental propagation. (#34820 by @jf-eirinha)export =so eslint-plugin-react-hooks emits correct types for consumers in Node16 ESM projects. (#34949 by @karlhorky)configs.flatso theconfigsexport is always defined. (#34950 by @poteto)v7.0.0Compare Source
This release slims down presets to just 2 configurations (
recommendedandrecommended-latest), and all compiler rules are enabled by default.recommended-latest-legacyandflat/recommendedconfigs. The plugin now providesrecommended(legacy and flat configs with all recommended rules), andrecommended-latest(legacy and flat configs with all recommended rules plus new bleeding edge experimental compiler rules). (@poteto in #34757)v6.1.1Compare Source
Note: 6.1.0 accidentally allowed use of
recommendedwithout flat config, causing errors when used with ESLint v9'sdefineConfig()helper. This has been fixed in 6.1.1.recommendedconfig for flat config compatibility. Therecommendedconfig has been converted to flat config format. Non-flat config users should userecommended-legacyinstead. (@poteto in #34700)recommended-latestandrecommended-latest-legacyconfigs that include React Compiler rules. (@poteto in #34675)NoUnusedOptOutDirectivesrule. (@poteto in #34703)hermes-parserand dependency. (@poteto in #34719)@babel/plugin-proposal-private-methodsdependency. (@ArnaudBarre and @josephsavona in #34715)v6.1.0Compare Source
Note: Version 6.0.0 was mistakenly released and immediately deprecated and untagged on npm. This is the first official 6.x major release and includes breaking changes.
recommendedpreset. Legacy config moved torecommended-legacy. (@michaelfaith in #32457)usewithin try/catch blocks. (@poteto in #34040)useEffectEventfunctions in arbitrary closures. (@jbrown215 in #33544)React.useEffectin addition touseEffectin rules-of-hooks. (@Ayc0 in #34076)react-hookssettings config option that to acceptadditionalEffectHooksthat are used across exhaustive-deps and rules-of-hooks rules. (@jbrown215) in #34497v6.0.0Compare Source
Accidentally released. See 6.1.0 for the actual changes.
thebuilder/react-intersection-observer (react-intersection-observer)
v10.0.0Compare Source
Based on the great work in #718 by @jantimon - This release adds the new
useOnInViewhook.✨ New
useOnInViewhook — a no-re-render alternative touseInViewthat delivers(inView, entry)to your callback while returning a ref you can attach to any element. Designed for tracking, analytics, and other side effect heavy workloads where state updates are unnecessary.IntersectionChangeEffect/IntersectionEffectOptionstypes — exported helper types that describe the new hook’s callback and options surface.useOnInView.useInView,useOnInView, and<InView>now ignore the browser’s initialinView === falseemission foronChangeevents, so handlers only fire once a real visibility change occurs, while still reporting all subsequent enter/leave transitions.🧪 Testing
useOnInView, covering thresholds,triggerOnce,skiptoggling, merged refs, and multiple observers on the same node.What's Changed
New Contributors
Full Changelog: thebuilder/react-intersection-observer@v9.16.0...v10.0.0
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.
This PR was generated by Mend Renovate. View the repository job log.