chore(deps): update react monorepo #11
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
149ffbd
to
a9f48f0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
a9f48f0
to
105507a
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
105507a
to
31277cc
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
31277cc
to
07bb5ed
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
07bb5ed
to
5305349
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
5305349
to
9ec5432
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
9ec5432
to
53a9240
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
53a9240
to
1662c49
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
1662c49
to
7afdcf2
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
7afdcf2
to
a54fb60
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
a54fb60
to
9f18b3a
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
9f18b3a
to
485dc0c
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
485dc0c
to
162f73c
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
162f73c
to
be53a9f
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
3 times, most recently
from
e310046
to
1b884a8
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
3 times, most recently
from
80149c9
to
47b051b
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
fe2c6d3
to
debc8c9
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
e5ec8c9
to
f077e33
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
f25b26a
to
e3d4402
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
d1b4792
to
d0a9760
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
d0a9760
to
621097f
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
3 times, most recently
from
0c548c0
to
4ee1cf9
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
052c11e
to
42c01b0
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
e8874c2
to
d2f518c
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
3 times, most recently
from
a07e19f
to
fa22858
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
e92bdd4
to
7fce21d
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
7fce21d
to
62c28e4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
16.9.46->16.14.4616.9.8->16.9.1916.13.1->16.14.04.8.2->4.28.016.13.1->16.14.0Release Notes
facebook/react (react)
v16.14.0Compare Source
React
facebook/react (react-devtools)
v4.28.0Compare Source
July 4, 2023
Features
Bugfixes
Other
v4.27.8Compare Source
May 17, 2023
Bugfixes
v4.27.7Compare Source
May 4, 2023
Bugfixes
v4.27.6April 20, 2023
Bugfixes
Other
v4.27.5April 17, 2023
Bugfixes
Other
v4.27.4Compare Source
March 24, 2023
Bugfixes
v4.27.3March 22, 2023
Bugfixes
Others
v4.27.2February 16, 2023
semverusages withcompare-versionsfor smaller bundle size (markerikson in #26122)v4.27.1December 6, 2022
v4.27.0November 28, 2022
Features
Bugfixes
v4.26.1Compare Source
October 13, 2022
v4.26.0September 16, 2022
displayNameis set (eps1lon in #21952)v4.25.0July 13, 2022
v4.24.7Compare Source
May 31, 2022
v4.24.6Compare Source
May 12, 2022
v4.24.5Compare Source
May 5, 2022
TreeContextreducer (bvaughn in #24501)forwardRefdid not render (lunaruan in #24494)formateWithStylesfunction (lunaruan in #24486)v4.24.4Compare Source
April 8, 2022
createStore()method to override Store config params (bvaughn in #24303)v4.24.3Compare Source
March 29, 2022
Bugfix
v4.24.2Compare Source
March 24, 2022
Bugfix
v4.24.1Compare Source
March 15, 2022
Bugfix
v4.24.0Compare Source
March 10, 2022
Feature
Bugfix
Errorstacks in DevTools error boundary (bvaughn in #24065)<TracingMarker>component boilerplate (lunaruan in #23275)Misc
Breaking change
Technically this is a breaking change for projects using
react-devtools-inline, but since this package already depends on the experimental release channel, we are going to include it in 4.24.v4.23.0January 24, 2022
Feature
Bugfix
Misc
v4.22.1December 14, 2021
require()statements inreact-devtools-inline(bvaughn in #22961)filesarray inreact-devtoolspackage.json(bvaughn in #22960)v4.22.0Compare Source
December 13, 2021
A note for React Native users
React DevTools has two main pieces:
This release updates the protocol that DevTools uses to communicate between the "frontend" and "backend" components.
Because React Native embeds a copy of the React DevTools "backend" (
react-devtools-core/backend), the "frontend" (UI) needs to match. This means you may be prompted to upgrade (or downgrade) your React DevTools based on which version of React Native your app uses.Features
Bugfix
Misc
v4.21.0Compare Source
October 31, 2021
Features
Bugfix
Misc
v4.20.2Compare Source
October 20, 2021
Bugfix
v4.20.1Compare Source
October 19, 2021
Bugfix
v4.20.0October 15, 2021
Features
Bugfix
Misc
v4.19.2October 8, 2021
Bugfix
v4.19.1October 1, 2021
Bugfix
v4.19.0September 29, 2021
Features
Bugfix
utfDecodeString()(bvaughn in #22330)Performance
network.onRequestFinished()caching withnetwork.getHAR()(bvaughn in #22285)v4.18.0September 1, 2021
Features
v4.17.0August 24, 2021
Features
Bugfix
source-maplibrary withsource-map-jsfor named hooks source map parsing (bvaughn in #22126)v4.16.0August 16, 2021
Features
Bugfix
v4.15.0August 11, 2021
Features
Bugfix
Misc
Scheduling profiler
What is React working on?
React’s previous Profiler primarily reports how fast (or slow) components are when rendering. It didn’t provide an overview of what React is doing (the actual cooperative scheduling bits). The new profiler does. It shows when components schedule state updates and when React works on them. It also shows how React categorizes and prioritizing what it works on.
Here’s a profile for a simple app that uses only the legacy (synchronous)
ReactDOM.renderAPI. The profiler shows that all of the work scheduled and rendered by this app is done at synchronous priority:Legacy-render-uses-the-synchronous-lane.mp4
Here’s a more interesting profile for an app that’s rendered at default priority using the new
createRootAPI, then updates synchronously in response to an “input” event to manage a "controlled component":Controlled-inputs-render-synchronously.mp4
Here’s part of a profile showing an idle app (no JavaScript running). In this case, React does some pre-rendering work for components that are “offscreen” (not currently displayed).
Offscreen-work-prerendered-during-idle.mp4
Note that “offscreen” refers to a new API and set of features that we haven’t talked about much yet except for some passing references. We’ll talk more about it in future posts.
What are “transitions” and how do they work?
We recently shared an update about the new
startTransitionAPI. This API helps apps feel responsive even when there are large updates by splitting the work into (1) a quick update to show that the app has received some input and (2) a slower update (the “transition”) that actually does any heavy lifting needed as a result of the input.Here is an example profile that uses the transition API. First React renders a small update that shows the user some visual feedback (like updating a controlled component or showing an inline loading indicator). Then it renders a larger update that, in this case, computes some expensive value.
Render-heavy-cpu-work-as-a-transition.mp4
How does Suspense impact rendering performance?
You may have heard mention of “suspense” in past talks or seen it referenced in our docs. Although full support for data fetching via Suspense is expected to be released sometime after React 18.0, you can use Suspense today for things like lazy-loading React components. The new profiler shows when components suspend during render and how that impacts overall rendering performance.
Here’s an example profile that suspends during the initial render to lazy-load a component using
React.lazy. While this component is loading, React shows a “fallback“ (placeholder UI). Once the component finishes loading, React retries the render and commits the final UI.Suspend-during-mount-to-lazy-load-component.mp4
We plan to expand support for Suspense in the coming weeks to more explicitly show when suspense fallbacks are rendered and which subsequent renders are related to an initial update that suspended.
What else might cause a render to get delayed?
Suspense can cause a render to get delayed as React waits for data to load, but React can also get stuck waiting on a lot of JavaScript to run.
React profiling tools have previously focused on only reporting what React (or React components) are doing, but any JavaScript the browser runs affects performance. The new profiler shows non-React JavaScript as well, making it easy to see when it delays React from rendering.
Rendering-blocked-by-other-JavaScript.mp4
What can you do to improve performance?
Until now, DevTools (and the Profiler) has provided information without commentary. The new profiler takes a more active approach– highlighting where we think performance can be improved and providing suggestions.
For example, suspending during an update is generally a bad user experience because it causes previously shown components to be unmounted (hidden) so the fallback can be shown while data loads. This can be avoided using the new Transition API. If you forget to add a transition to an update that suspends, the new profiler will warn you about this:
Dont-suspend-during-an-update.mp4retry.mp4
The new profiler also warns about scheduling a long, synchronous React update inside of event handler.
Dont-schedule-long-synchronous-updates-in-event-handlers.mp4
Another thing the new profiler will warn about is long-running renders scheduled from layout effects (
useLayoutEffectorcomponentDidMount/componentDidUpdate). These updates (called “nested updates”) are sometimes necessary to adjust layout before the browser paints, but they should be fast. Slow nested updates make the browser feel unresponsive.Long-nested-updates-delay-paint.mp4
v4.14.0July 17, 2021
Features
Display hook names for inspected components
Control for manually toggling error boundaries
v4.13.5May 25, 2021
Bugfix
v4.13.4May 20, 2021
Bugfix
v4.13.3May 19, 2021
Misc
reactandreact-domAPI imports in preparation for upcoming stable release (bvaughn in #21488)Bugfix
useState()object withhasOwnPropertykey (bvaughn in #21524)Symbolwas logged toconsole.errororconsole.warn(bvaughn in #21521)(bvaughn in 9cf1069)
v4.13.2May 7, 2021
Misc
v4.13.1April 28, 2021
Bugfix
React.memocomponents (bvaughn in #21392)Misc
v4.13.0April 28, 2021
Features
Bugfix
Bridge protocol version backend/frontend
During initialization, DevTools now checks to ensure it's compatible with the "backend" that's embedded within a renderer like React Native. If the two aren't compatible, upgrade instructions will be shown:
Learn more about this change at fb.me/devtools-unsupported-bridge-protocol
v4.12.4April 19, 2021
Bugfix
@octokit/restdependency because of a problem with transitive dependencies (bvaughn in #21317)v4.12.3April 19, 2021
Bugfix
v4.12.2April 16, 2021
Bugfix
v4.12.1April 14, 2021
Although this release is being made for all NPM packages, only the
react-devtools-inlinepackage contains changes.Bugfix
react-devtools-inlinebug in frontendinitializemethod (bvaughn in #21265)v4.12.0April 12, 2021
Although this release is being made for all NPM packages, only the
react-devtools-inlinepackage contains changes.Features
createBridgeandcreateStoreexports to thereact-devtools-inline/frontendentrypoint to support advanced use cases (bvaughn in #21032)v4.11.0April 9, 2021
Bugfix
$rshould contain hooks property when it isforwardReformemocomponent (meowtec in #20626)sync-xhris allowed before reload and profile (ChrisDobby in #20879)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.
This PR has been generated by Mend Renovate. View repository job log here.