Marvin Hagemeister
Marvin Hagemeister
@andrewiggins pointed us to [this tweet](https://twitter.com/kenneth_chau/status/1318064261994749952) which points to a benchmark of dev mode for bundlers. It's a project with 3k components. https://github.com/kenotron/scale-test Tried it with wmr and we run...
#### Input Code ```js const foo = "foo"; const bar = `asdf ${foo} asd ${foo}` ``` [Babel REPL link](https://babeljs.io/repl#?babili=true&browsers=&build=&builtIns=false&code_lz=MYewdgzgLgBAZiEMC8MBECRoNwChSSwBGAhgE4owAGJAJiRLTACQDemAvjA0251UA&debug=false&forceAllTransforms=false&shippedProposals=false&circleciRepo=&evaluate=true&fileSize=false&lineWrap=false&presets=babili&prettier=false&targets=Node-8.7&version=7.0.0-beta.38&envVersion=) #### Actual Output ```js traverse.clearCache is not a function. (In 'traverse.clearCache()',...
The default output doesn't have much contrast and is a bit hard to read for me. That's best illustrated with a screenshot: 
`micro-dev` is really awesome some for. Love the attention to detail you put into it and the hot reloading is ace. There is one thing that is bugging me though...
This allows the extension to properly filter over framework internal root nodes without resorting to local hacks.
It's essentially a more powerful `performance.measure()` alternative that captures additional details that's exclusive to extensions like CPU load. Links: - https://gist.github.com/bvaughn/8de925562903afd2e7a12554adcdda16 - https://github.com/facebook/react-devtools/pull/1069 - https://addyosmani.com/assets/images/4324242.jpg - https://addyosmani.com/assets/images/[email protected] - https://user-images.githubusercontent.com/29597/43925307-c81d5b76-9bdb-11e8-9273-1d9229ac5815.png
Suggestion via slack: > One thing that also I’d love to know during debugging is if a certain compnent was remounted (aka now has new identity) or not. I’m trying...
Add more information to render reasons for hooks. The current message is a bit generic and doesn't hint at which hook changed. Idea: ` useState()#1: newValue`
We currently display `Portals` like standard class components. We don't have special handling for the newly rendered sub tree which is why it renders it as if it would be...