Skip to content
Switch branches/tags
Go to file
10 contributors

Users who have contributed to this file

@jstejada @lunaruan @gaearon @mondaychen @shubham9411 @NE-SmallTown @morgsmccauley @bbolek @bvaughn @k1499
1019 lines (708 sloc) 68.1 KB

React DevTools changelog


May 31, 2022

  • mock requestAnimationFrame with setTimeout as a temporary fix for #24626 (mondaychen in #24633)
  • Fix formatWithStyles not styling the results if the first argument is an object + Added unit tests (lunaruan in #24554)


May 12, 2022

  • fix a bug in console.log with non-string args (mondaychen in #24546)
  • Add Pragma to Only Run Tests if Version Requirement Satisfied (lunaruan in #24533)
  • [DevTools][Bug] Fix Race Condition When Unmounting Fibers (lunaruan in #24510)
  • [React DevTools] Improve DevTools UI when Inspecting a user Component that Throws an Error (mondaychen in #24248)


May 5, 2022

  • Fixed potential undefined error in TreeContext reducer (bvaughn in #24501)
  • Fix error where Profiler sometimes incorrectlyed reported that a forwardRef did not render (lunaruan in #24494)
  • Fix regex for formateWithStyles function (lunaruan in #24486)
  • Fixed wrong method call for LRU cache (bvaughn in #24477)
  • Synchronize implementations of second render logging (billyjanitsch in #24381)
  • Don't stringify objects for console log second render (lunaruan in #24373)


April 8, 2022

  • Allow react-devtools-inline createStore() method to override Store config params (bvaughn in #24303)
  • [ReactDebugTools] wrap uncaught error from rendering user's component (mondaychen in #24216)


March 29, 2022


  • Profiler should only report stateful hooks that change between renders (bvaughn in #24189)
  • Ignore duplicate welcome "message" events (bvaughn in #24186)
  • Attach DevTools Tree keyboard events to the Tree container (not the document) (bvaughn in #24164)


March 24, 2022


  • Show upgrade/downgrade instructions inline for errors thrown by the Store due to incompatible protocol (mismatched backend and frontend versions) (bvaughn in #24147)
  • Inspecting an element in a nested renderer no longer throws (lunaruan in #24116)


March 15, 2022


  • Disable unsupported Bridge protocol version dialog and add workaround for old protocol operations format (bvaughn in #24093)


March 10, 2022


  • Show DevTools backend and frontend versions in UI (bvaughn in #23399)
  • Timeline profiler refactored to support reading basic profiling data directly from React (bvaughn in #22529)



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.


January 24, 2022


  • DevTools: Only show StrictMode badge on root elements (bvaughn in #23012)


  • Don't crawl unmounted subtrees when profiling starts (bvaughn in #23162)
  • Filter deleted components from the updaters list to avoid runtime errors later (lunaruan in #23156)


  • DevTools (not React) logs Timeline performance data to the User Timing API (bvaughn in #23102)


December 14, 2021

  • Fix invalid require() statements in react-devtools-inline (bvaughn in #22961)
  • Fix invalid files array in react-devtools package.json (bvaughn in #22960)


December 13, 2021

A note for React Native users

React DevTools has two main pieces:

  • The frontend users interact with (the Components tree, the Profiler, etc.).
  • The backend which runs in the same context as React itself. (In the web page with React DOM or shipped on the device with the React Native runtime.)

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.



  • DevTools should inject itself for XHTML pages too (not just HTML) (@bvaughn in #22932)
  • Don't restore profiling data if we're profling (@eps1lon in #22753)
  • DevTools should properly report re-renders due to (use)context changes (@bvaughn in #22746)
  • Filter empty commits (all Fibers bailed out) from Profiler (@bvaughn in #22745)
  • Accept json file in import fileinput (@jyash97 in #22717)
  • Expose css vars to reach-ui portal components (@jyash97 in #22716)
  • Fix DevTools advanced tooltip display conditional check (@bvaughn in #22669)


  • Emit new event when DevTools connects in standalone app (@jstejada in #22848)


October 31, 2021


  • Scheduling Profiler: Add marks for component effects (mount and unmount) (@bvaughn in #22578)
  • Scheduling Profiler: De-emphasize React internal frames (bvaughn in #22588)


  • Revert logic for checking for duplicate installations of DevTools potentially causing issues loading Components tab (@jstejada in #22638)
  • Scheduling Profiler does not warn about long transitions (@bvaughn in #22614)
  • Re-enable 'Reload and Start Profiling' for Microsoft Edge (@eoandersson in #22631)



October 20, 2021


  • Dev Tools: Relax constraint on passing extensionId for backend init (@jstejada in #22597)
  • DevTools: Fix passing extensionId in evaled postMessage calls (@jstejada in #22590)


October 19, 2021


  • Only show DevTools warning about unrecognized build in Chrome (@jstejada in #22571)
  • DevTools: Include Edge in browser name detection (@jstejada in #22584)


October 15, 2021


  • Allow to use the Profiler when no client is connected in standalone DevTools (@gabrieltrompiz in #22551)


  • Surface backend errors during inspection in the frontend UI (@bvaughn in #22546)
  • Prevent splash page in standalone app from becoming unresponsive after the disconnection of a client (#22558) (@gabrieltrompiz in #22560)
  • Prevent errors/crashing when multiple installs of DevTools are present (@jstejada in #22517)
  • Update Fiber logic in backend renderer to match implementation in React (@jstejada in #22527)


  • Show warning in UI when duplicate installations of DevTools extension are detected (@jstejada in #22563)
  • Improved filenames of built worker files (@akgupta0777 in #22559)


October 8, 2021


  • Show different error boundary UI for timeouts than normal errors (bvaughn in #22483)
  • Fixed bug where deleting a component filter would also close the settings modal (Biki-das in #22484)


October 1, 2021


  • Fixed potential cache miss when insepcting elements (bvaughn in #22472)


September 29, 2021


  • Scheduling Profiler: Show Suspense resource .displayName (bvaughn in #22451)
  • Scheduling Profiler marks should include thrown Errors (bvaughn in #22419)
  • Don't patch console during first render in strict mode (lunaruan in #22308)
  • Show which hook indicies changed when profiling for all builds (bvaughn in #22365)
  • Display actual ReactDOM API name in root type (eps1lon in #22363)
  • Add named hooks support to standalone and inline DevTools (jstejada in #22320 and bvaughn in #22263)


  • DevTools encoding supports multibyte characters (e.g. "🟩") (bvaughn in #22424)
  • Improve DEV errors if string coercion throws (Temporal.*, Symbol, etc.) (justingrant in #22064)
  • Fix memory leak caused by not storing alternate Fiber pointer (bvaughn in #22346)
  • Fix call stack exceeded error in utfDecodeString() (bvaughn in #22330)
  • Fix runtime error when inspecting an element times out (jstejada in #22329)


  • DevTools: Lazily parse indexed map sections (bvaughn in #22415)
  • DevTools: Hook names optimizations (bvaughn in #22403)
  • Replaced network.onRequestFinished() caching with network.getHAR() (bvaughn in #22285)


September 1, 2021


  • DevTools: Improve named hooks network caching (bvaughn in #22198)
  • Console Logging for StrictMode Double Rendering (lunaruan in #22030)



August 24, 2021


  • Scheduling Profiler: Add network measures (bvaughn in #22112)
  • Add options for disabling some features (hbenl in #22136)



August 16, 2021



  • split parsing code to unblock Firefox release (lunaruan in #22102)
  • Scheduling profiler: Canvas views clip by default (bvaughn in #22100)
  • Fixed Components tree indentation bug for Chrome extension (bvaughn in #22083)


August 11, 2021




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.render API. The profiler shows that all of the work scheduled and rendered by this app is done at synchronous priority:


Here’s a more interesting profile for an app that’s rendered at default priority using the new createRoot API, then updates synchronously in response to an “input” event to manage a "controlled component":


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


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 startTransition API. 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.

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.


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.

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:


The new profiler also warns about scheduling a long, synchronous React update inside of event handler.


Another thing the new profiler will warn about is long-running renders scheduled from layout effects (useLayoutEffect or componentDidMount/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.



July 17, 2021


Display hook names for inspected components

DevTools parsing hook names

Control for manually toggling error boundaries

DevTools error boundary toggle


May 25, 2021


  • Handle edge case where a component mounts before its "owner" (in DEV mode) that previously caused a validation error (bvaughn in #21562)


May 20, 2021


  • Fix edge-case Fast Refresh bug that caused Fibers with warnings/errors to be untracked prematurely (which broke componentinspection in DevTools) (bvaughn in #21536)
  • Revert force deep re-mount when Fast Refresh detected (was no longer necessary) (bvaughn in #21539)


May 19, 2021


  • Updated react and react-dom API imports in preparation for upcoming stable release (bvaughn in #21488)


  • Reload all roots after Fast Refresh force-remount (to avoid corrupted Store state) (bvaughn in #21516 and #21523)
  • Errors thrown by Store can be dismissed so DevTools remain usable in many cases (bvaughn in #21520)
  • Bugfix for useState() object with hasOwnProperty key (bvaughn in #21524)
  • Fixed string concatenation problem when a Symbol was logged to console.error or console.warn (bvaughn in #21521)
  • DevTools: Fixed version range NPM syntax (bvaughn in 9cf1069)
  • Tweaked DevTools error template title to match issue form template (bvaughn in 1a2d792)


May 7, 2021



April 28, 2021


  • Improve display name logic for React.memo components (bvaughn in #21392)
  • Fixed potential runtime error with Suspense in versions <= 17 (bvaughn in #21432)
  • Errors thrown in the Store are no longer silent (bvaughn in #21426)



April 28, 2021


  • Add Bridge protocol version backend/frontend (bvaughn in #21331)


  • DevTools iterates over siblings during mount (rather than recursing) to avoid stack overflow errors (bvaughn in #21377)
  • Multiple error dialogs can be visible at once (bvaughn in #21370)
  • Console patching should handle Symbols without erroring (bvaughn in #21368)
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:

Dialog displaying downgrade instructions for the React DevTools frontend to connect to an older backend version

Dialog displaying upgrade instructions for the React DevTools frontend to connect to a newer backend version

Learn more about this change at


April 19, 2021


  • Remove @octokit/rest dependency because of a problem with transitive dependencies (bvaughn in #21317)


April 19, 2021


  • Wrapped quotation marks around Fiber ids or indices for all DevTools errors to better support GitHub fuzzy error search (bvaughn in #21314)


April 16, 2021


  • DevTools reliably suppresses console logs when generating component stacks (bvaughn in #21301)


April 14, 2021 Although this release is being made for all NPM packages, only the react-devtools-inline package contains changes.


  • Fixed react-devtools-inline bug in frontend initialize method (bvaughn in #21265)


April 12, 2021 Although this release is being made for all NPM packages, only the react-devtools-inline package contains changes.


  • Added createBridge and createStore exports to the react-devtools-inline/frontend entrypoint to support advanced use cases (bvaughn in #21032)


April 11, 2021


  • Fixed broken import in react-devtools-inline for feature flags file (bvaughn in #21237)


April 9, 2021


  • $r should contain hooks property when it is forwardRef or memo component (meowtec in #20626)
  • Ensure sync-xhr is allowed before reload and profile (ChrisDobby in #20879)
  • Bump electron version from 9.1.0 to 11.1.0 for darwin-arm64 builds (jaiwanth-v in #20496)
  • Fixed primitive hook badge colors for light theme (bvaughn in #21034)
  • Increased minimum Chrome/Firefox versions from 51/54 to 60/55 to reduce polyfill code. (bvaughn in #21185)
  • Fix can't expand prop value in some scenario (iChenLei in #20534)
  • Flush updated passive warning/error info after delay (bvaughn in #20931)
  • Patch console methods even when only show-inline-warnings/errors enabled (bvaughn in #20688)
  • React Native fixes for new inline errors feature (bvaughn in #20502)
  • Fixed invalid work tag constants that affected a certain range of React versions (bvaughn in #20362)


Experimental features

The following features are only enabled when used with (experimental) builds of React:

Improve Profiler commit-selector UX

Video demonstrating tooltip with commit duration and time

Graphic illustrating Profiler bar heights using different scales

Expose DEV-mode warnings in devtools UI

Inline warnings and errors

Shows which fibers scheduled the current update

Shows which fibers scheduled the current update

Add commit and post-commit durations to Profiler UI

Add commit and post-commit durations to Profiler UI

Show which hooks (indices) changed when profiling

Show which hooks (indices) changed when profiling


May 20, 2021


  • Ported passive effects sync flushing/bubbling bugfix (bvaughn in #21540)


April 27, 2021


  • Replaced Facebook-internal link with public link for Bridge protocol mismatch info page (bvaughn in #21344)


April 27, 2021


  • Added Bridge protocol check and warning dialog if embedded DevTools backend is incompatible with DevTools UI (bvaughn in #21344)


November 12, 2020



November 12, 2020


  • Make DevTools Websocket retry delay configurable (bvaughn in #20107)


  • Fix error loading source maps for devtools extension (sytranvn in #20079)
  • Remove css-sourcemap for react-devtools-inline (sean9keenan in #20170)
  • Decrease NPM update notification/prompt for standalone DevTools (recurx in #20078)


October 19, 2020



  • Show proper icon/tooltip for restricted browser pages (sktguha in #20023)
  • Fix emoji character shown in Chrome developer tools panel (bvaughn in #19603)
  • Don't open two tabs in Firefox when clicking on troubleshooting instructions (unbyte in #19632)
  • Support inner component _debugOwner in memo (bvaughn in #19556)
  • Proxied methods should be safely dehydrated for display (@pfongkye in b6e1d08
  • Property list values should show whitespace (sammarks in #19640)
  • Fix crash when inspecting document.all (omarsy in #19619)
  • Don't call generators during inspection since they may be stateful (todortotev in #19831)
  • Fix bad null check in DevTools highlight code (bvaughn in #20010)
  • Handled a missing suspense fiber when suspense is filtered on the profiler (IDrissAitHafid in #ISSUE)
  • Fixed unfound node error when Suspense is filtered (IDrissAitHafid in #20019)
  • Always overrides the dispatcher when shallow rendering (bvaughn in #20011)
  • Frevent phishing attacks (iamwilson in #19934)


Improved DevTools editing interface

Improved parsing Value parsing logic has been relaxed so as to no longer require quotes around strings or double quotes: looser parsing logic

Modifying arrays New values can be added to array props/state/hooks now. Existing values can also be deleted: adding and removing values from an array

Modifying objects New keys can be added to object props/state/hooks now. Existing keys can be renamed or deleted entirely: adding/renaming/removing object properties


July 15, 2020



July 10, 2020


  • Fix break-on-warning to truly be off by default. (gaearon in #19309)


July 9, 2020



  • Updates Electron version for react-devtools to pull in several security fixes (gsimone in #19280)
  • Remove unnecessary tag end from CommitRanked view (finico in #19195)
  • Shutdown DevTools Bridge synchronously when unmounting (bvaughn in #19180)


May 18, 2020


  • Improved appended component stacks for third party warnings to be more like native (bvaughn in #18656)
  • Improve inline search results by highlighting match on HOC badge (bl00mber in #18802)
  • Add key badge to inspected element in right hand pane ([karlhorky]]( in #18737)
  • Improve Profiler snapshot selector drag-and-drop UX (bl00mber in #18852)
  • Profiler tooltip now includes self duration to make it easier to scan times without requiring selection (bvaughn in #18510)
  • Rendered by list also now highlights native elements on hover (hristo-kanchev in #18479)
  • Add in-page highlighting for mouse-over interactions in Profiler (bl00mber in #18745)


  • Fix Profiler bug "Could not find commit data for root" by resetting selected node on root change (bl00mber in #18880)
  • Add imported flag to Profiling data to more reliably differentiate between imported and session data (bl00mber in #18913)
  • Disable Profiler filtering to avoid edge case runtime error "Cannot read property 'duration' of undefined" (bvaughn in #18862)
  • Fix Profiler bug "cannot read property 'memoizedState' of null" (bvaughn in #18522)
  • Whitespace search results highlighting bug fix (bvaughn in #18527)
  • Improved confusing Profiler tooltip text for components that did not render (bvaughn in #18523)
  • Fix edge case performance issue when highlight elements enabled (Faelivrinx in #18498)
  • Disabled Webpack auto polyfill for setImmediate (bvaughn in #18860)
  • Fix mouse interactions for standalone DevTools on Linux (bl00mber in #18772)


March 26, 2020



  • Improve display of complex values for useDebugValue (eps1lon in #18070)
  • Fix minor CSS layout issue that broke Profiler commit selector UI (bvaughn in #18286)
  • Inlined DevTools event emitter implementation to fix a source of Profiler bugs (bvaughn in #18378)


  • Remove "es6-symbol" dependency from "react-devtools-inline" package (bvaughn in #18397)


March 3, 2020



  • Improve how empty commits are filtered (nutboltu in #17931)
  • BigInt serialize issue in devtools copy to clipboard (bvaughn in #17771)
  • Renamed "backend.js" to "react_devtools_backend.js" to reduce potential confusion from profiling (bvaughn in #17790)
  • Update root styles to prevent box-sizing style from leaking outside of inline target (GasimGasimzada in #17775)
  • Fix "Cannot read property 'sub' of undefined" error when navigating to plain-text pages (wfnuser in #17848)
  • Fix potential error with composite hooks during shallow re-rendering (bvaughn in #18130)
  • Scope dev tools wildcard styles within DevTools CSS class (@GasimGasimzada in 9cc094a)
Info summary tooltips

Profiler tooltips in Flamegraph chart

Profiler tooltips in Ranked chart

Components panel resize

Horizontal Components panel resizing

Vertical Components panel resizing


January 3, 2020


  • Re-enabled "copy" prop/state/hooks context menu option for Firefox (bvaughn,rpl in #17740)
  • Shift+Enter focuses previous search result in Components tree (Bo-Duke in #17005)
  • Properly display formatted RegExp values in props/state panel(bvaughn in #17690)
  • Profiler commit selector wraps around for easier navigation of large profiles (bvaughn in #17760)


  • Check document.contentType before injecting hook to avoid breaking XML file syntax highlighting in Firefox (bvaughn in #17739)
  • Fix standalone UI not responding to mouse interactions due to webkit-app-region style (cwatson88 in #17584)
  • Support inspecting object values with null protos (bvaughn in #17757)
  • Support inspecting values that have overridden hasOwnProperty attribute (bvaughn in #17768)
  • Fixed regression that made Profiler "Could not find node…" error happen more frequently (bvaughn in #17759)


December 20, 2019


  • Show component location for selected element in bottom/right panel (bvaughn in #17567)
  • Improved inspected element values with inline previews (bvaughn in #17579)
  • Improved selection and toggling for inspected element panel (bvaughn in #17588)
  • Copy context menu for inspecting and copying props/state/hooks/context values (bvaughn in #17608)

Bug fixes

  • Fix serialization for BigInt type so that it does not break inspection panel. (nutboltu in #17233)
  • Fix display name logic for forwardRefs that use displayName property (zthxxx in #17613)


November 27, 2019

Bug fixes

  • Profiler automatically filters certain types of empty (no work) commits. (bvaughn in #17253)
  • Fix memoized components showing as "Anonymous" in Components tab. (wsmd in #17274)
  • Edge-case bugfix for non-string element keys. (bvaughn in #17164)


October 3, 2019


  • "Highlight updates" feature added for browser extensions and react-devtools-inline NPM package. (bvaughn in #16989)


September 30, 2019

Bug fixes

  • Fixed regression where DevTools wouldn't properly connect with apps when using the file:// protocol. (linshunghuang in #16953)


September 27, 2019

Bug fixes

  • Fixed an infinite loop that occurred in some cases with prop values of NaN. (bvaughn in #16934)


September 26, 2019

Bug fixes

  • Fixed bug where Components panel was always empty for certain users. (linshunghuang in #16900)
  • Fixed regression in DevTools editable hooks interface that caused primitive values to be shown as undefined. (bvaughn in #16867)
  • Fixed bug where DevTools showed stale values in props/state/hooks editing interface. (bvaughn in #16878)
  • Show unsupported version dialog with downgrade instructions. (bvaughn in #16897)


September 19, 2019


  • Props/state editor supports adding new values and changing value types. (hristo-kanchev in #16700)

Bug fixes

  • Profiler correctly saves/exports profiling data in Firefox now. (hristo-kanchev in #16612)
  • Class components now show "legacy context" header (rather than "context") for legacy API. (hristo-kanchev in #16617)
  • Show component source button ("<>") now highlights the render method for class components. (theKashey in #16759)
  • Bugfix for components with non-standard object values for (LetItRock in #16798)


August 26, 2019

Bug fixes

  • Remove ⚛️ emoji prefix from Firefox extension tab labels
  • Standalone polyfills Symbol usage


August 19, 2019

Bug fixes

  • Props, state, and context values are alpha sorted.
  • Standalone DevTools properly serves backend script over localhost:8097


August 18, 2019

Bug fixes

  • Bugfix for potential error if a min-duration commit filter is applied after selecting a fiber in the Profiler UI.


August 17, 2019

Bug fixes

  • ES6 Map and Set, typed arrays, and other unserializable types (e.g. Immutable JS) can now be inspected.
  • Empty objects and arrays now display an "(empty)" label to the right to reduce confusion.
  • Components that use only the useContext hook now properly display hooks values in side panel.
  • Style editor now supports single quotes around string values (e.g. both "red" and 'red').
  • Fixed edge case bug that prevented profiling when both React v16 and v15 were present on a page.


August 15, 2019

Permissions cleanup

  • Removed unnecessary webNavigation permission from Chrome and Firefox extensions.


August 15, 2019

Permissions cleanup

  • Removed unnecessary <all_urls>, background, and tabs permissions from Chrome and Firefox extensions.


August 15, 2019

General changes

Improved performance

The legacy DevTools extension used to add significant performance overhead, making it unusable for some larger React applications. That overhead has been effectively eliminated in version 4.

Learn more about the performance optimizations that made this possible.

Component stacks

React component authors have often requested a way to log warnings that include the React "component stack". DevTools now provides an option to automatically append this information to warnings (console.warn) and errors (console.error).

Example console warning with component stack added

It can be disabled in the general settings panel:

Settings panel showing "component stacks" option

Components tree changes

Component filters

Large component trees can sometimes be hard to navigate. DevTools now provides a way to filter components so that you can hide ones you're not interested in seeing.

Component filter demo video

Host nodes (e.g. HTML <div>, React Native View) are now hidden by default, but you can see them by disabling that filter.

Filter preferences are remembered between sessions.

No more inline props

Components in the tree no longer show inline props. This was done to make DevTools faster and to make it easier to browse larger component trees.

You can view a component's props, state, and hooks by selecting it:

Inspecting props

"Rendered by" list

In React, an element's "owner" refers to the thing that rendered it. Sometimes an element's parent is also its owner, but usually they're different. This distinction is important because props come from owners.

Example code

When you are debugging an unexpected prop value, you can save time if you skip over the parents.

DevTools v4 adds a new "rendered by" list in the right hand pane that allows you to quickly step through the list of owners to speed up your debugging.

Example video showing the "rendered by" list

Owners tree

The inverse of the "rendered by" list is called the "owners tree". It is the list of things rendered by a particular component- (the things it "owns"). This view is kind of like looking at the source of the component's render method, and can be a helpful way to explore large, unfamiliar React applications.

Double click a component to view the owners tree and click the "x" button to return to the full component tree:

Demo showing "owners tree" feature

No more horizontal scrolling

Deeply nested components used to require both vertical and horizontal scrolling to see, making it easy to "get lost" within large component trees. DevTools now dynamically adjusts nesting indentation to eliminate horizontal scrolling.

Video demonstration dynamic indentation to eliminate horizontal scrolling

Improved hooks support

Hooks now have the same level of support as props and state: values can be edited, arrays and objects can be drilled into, etc.

Video demonstrating hooks support

Improved search UX

Legacy DevTools search filtered the components tree to show matching nodes as roots. This made the overall structure of the application harder to reason about, because it displayed ancestors as siblings.

Search results are now shown inline similar to the browser's find-in-page search.

Video demonstrating the search UX

Higher order components

Higher order components (or HOCs) often provide a custom displayName following a convention of withHOC(InnerComponentName) in order to make it easier to identify components in React warnings and in DevTools.

The new Components tree formats these HOC names (along with several built-in utilities like React.memo and React.forwardRef) as a special badge to the right of the decorated component name.

Screenshot showing HOC badges

Components decorated with multiple HOCs show the topmost badge and a count. Selecting the component shows all of the HOCs badges in the properties panel.

Screenshot showing a component with multiple HOC badges

Restoring selection between reloads

DevTools now attempts to restore the previously selected element when you reload the page.

Video demonstrating selection persistence

Suspense toggle

React's experimental Suspense API lets components "wait" for something before rendering. <Suspense> components can be used to specify loading states when components deeper in the tree are waiting to render.

DevTools lets you test these loading states with a new toggle:

Video demonstrating suspense toggle UI

Profiler changes

Reload and profile

The profiler is a powerful tool for performance tuning React components. Legacy DevTools supported profiling, but only after it detected a profiling-capable version of React. Because of this there was no way to profile the initial mount (one of the most performance sensitive parts) of an application.

This feature is now supported with a "reload and profile" action:

Video demonstrating the reload-and-profile feature


Profiler data can now be exported and shared with other developers to enable easier collaboration.

Video demonstrating exporting and importing profiler data

Exports include all commits, timings, interactions, etc.

"Why did this render?"

"Why did this render?" is a common question when profiling. The profiler now helps answer this question by recording which props and state change between renders.

Video demonstrating profiler "why did this render?" feature

Because this feature adds a small amount of overhead, it can be disabled in the profiler settings panel.

Component renders list

The profiler now displays a list of each time the selected component rendered during a profiling session, along with the duration of each render. This list can be used to quickly jump between commits when analyzing the performance of a specific component.

Video demonstrating profiler's component renders list