react-devtools-experimental

Experimental rewrite of the React DevTools extension

Web Development

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

0Explicit recommenders

954GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Experimental rewrite of the React DevTools extension

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2019-05-21 15:15:01 UTC to 2019-08-16 02:20:43 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
May 20	2019-05-20 00:00:00 UTC	2019-05-27 00:00:00 UTC	1	1
May 27	2019-05-27 00:00:00 UTC	2019-06-03 00:00:00 UTC	0	0
Jun 3	2019-06-03 00:00:00 UTC	2019-06-10 00:00:00 UTC	0	0
Jun 10	2019-06-10 00:00:00 UTC	2019-06-17 00:00:00 UTC	0	0
Jun 17	2019-06-17 00:00:00 UTC	2019-06-24 00:00:00 UTC	0	0
Jun 24	2019-06-24 00:00:00 UTC	2019-07-01 00:00:00 UTC	0	0
Jul 1	2019-07-01 00:00:00 UTC	2019-07-08 00:00:00 UTC	0	0
Jul 8	2019-07-08 00:00:00 UTC	2019-07-15 00:00:00 UTC	0	0
Jul 15	2019-07-15 00:00:00 UTC	2019-07-22 00:00:00 UTC	0	0
Jul 22	2019-07-22 00:00:00 UTC	2019-07-29 00:00:00 UTC	0	0
Jul 29	2019-07-29 00:00:00 UTC	2019-08-05 00:00:00 UTC	0	0
Aug 5	2019-08-05 00:00:00 UTC	2019-08-12 00:00:00 UTC	0	0
Aug 12	2019-08-12 00:00:00 UTC	2019-08-19 00:00:00 UTC	2	2

What Hacker News says

3 sources

brianvaughn·Aug 16, 2019

> but Facebook is the last company I'd want to have the obscene privileges that extensions have. reply Sounds like you're talking about extensions in general, but for what it's worth- React DevTools doesn't require any super deep permissions¹ and all of the source code is in the open². ¹ https://github.com/bvaughn/react-devtools-experimental/blob/... ² https://github.com/bvaughn/react-devtools-experimental/tree/...

In New React DevTools

danabramov·Aug 16, 2019

If you saw the scary permission dialog upgrading, that was due to our mistake: https://twitter.com/reactjs/status/1162174507391574017. Commits with fixes: * https://github.com/bvaughn/react-devtools-experimental/commi... * https://github.com/bvaughn/react-devtools-experimental/commi... Both of these issues should be fixed in 4.0.2. Brian goes into more detail on why we originally added these permissions during the rewrite, and why we were able to remove them: https://www.reddit.com/r/reactjs/comments/cqx554/introducing.... (TLDR: some were for features we ended up cutting; others had easier workarounds that didn't need these permissions.) The source code is here (https://github.com/bvaughn/react-devtools-experimental/commi...). We're currently moving it into React repo so it's easier to find (https://github.com/facebook/react/pull/16381)

Read the rest

but haven't managed to make the CI green so the source of truth for releases is still in that branch. We plan to cut over to React repo as source of truth next week.

In New React DevTools

acemarke·May 21, 2019

Hey, that's my links list! :) Hope that's helpful! While it's probably not 100% relevant, you might also want to glance at some of the things I've done trying to benchmark performance for the React-Redux library itself, including running benchmarks in Puppeteer and capturing metrics like render times and FPS [0]. Now, my experience has been that I have to deliberately crank up the number of components on screen and dispatch absurd numbers of Redux actions a second just to get the FPS to drop below 60FPS, so I'm not sure how much that would be applicable to real-world apps, but at least you can see how I've tried to capture the values. As a general observation, I'd highly encourage folks to use the Profiler that's built into the React DevTools to view render behavior and find components that may be re-rendering when it wasn't necessary [1

Read the rest

] [2]. Also, Brian Vaughn has been working on a major rewrite of the React DevTools to both improve internal speed and add new features, and you can play around with it now [3]. Finally, if you _really_ want to get fine-grained, there's a little-known profiling/tracing API that can be used to capture render times in parts of your app [4] [5] [6]. [0] https://github.com/reduxjs/react-redux-benchmarks [1] https://reactjs.org/blog/2018/09/10/introducing-the-react-pr... [2] https://www.netlify.com/blog/2018/08/29/using-the-react-devt... [3] https://github.com/bvaughn/react-devtools-experimental [4] https://github.com/bvaughn/rfcs/blob/profiler/text/0000-prof... [5] https://gist.github.com/bvaughn/8de925562903afd2e7a12554adcd... [6] https://gist.github.com/bvaughn/25e6233aeb1b4f0cdb8d8366e54a...

In Ask HN: How to performance test React webapps for rendering speed regressions?