repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
facebookreact | why only one component can be render at root div | Question | I call two render method to same root div renderdom render navigation document getelementbyid root renderdom render app document getelementbyid root and what I get render on my screen be only a app component just want to know that the one render method override the previous render method |
facebookreact | error could not find node with i d 312 in commit tree | Bug | describe what you be do when the bug occur 1 I be profile a grid performance when render with 100 row 2 then I be move between the profiled datum 3 when click on the ranked tab the console show error and a button to report it please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 51 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | unexpected function component call use usestate | Question | do you want to request a feature or report a bug question what be the current behavior typescript import react usestate useeffect from react import reactdom from react dom import style css function child console log child render return null function app const count setcount usestate 0 console log render useeffect console log count change count count return usestate click count setcount count 1 1 setcount count 0 const rootelement document getelementbyid root reactdom render rootelement there be two button in this count example click one make count 1 another make count no change if click the no change button first render will not be log but if click the 1 button first and then click anthor render will show twice but child render will only show once I find the explain in document if you update a state hook to the same value as the current state react will bail out without render the child or firing effect react use the object be comparison algorithm do react only promise that child component will not be render in this situation the current component may still be render this be an example in sandbox which version of react and which browser os be affect by this issue do this work in previous version of react react 16 12 0 react dom 16 12 0 |
facebookreact | devtool crash levelchildren be undefined when select a component in flamegraph view | Bug | do you want to request a feature or report a bug bug what be the current behavior react devtool crash in the code below because levelchildren be undefined l456 l462 callstack be backend js format 6593 uncaught typeerror can not read property push of undefined at s backend js format 6593 at backend js format 6638 at inspecthooksoffiber backend js format 6682 at rt backend js format 2372 at object inspectelement backend js format 2753 at t backend js format 3484 at t r emit backend js format 978 at backend js format 7407 at t backend js format 4954 I haven t be able to reproduce this yet outside my app but here s the step that trigger the crash in my app 1 open dev tool 2 start profile 3 stop profile 4 select the calendarmiddle component in the flamegraph view 5 crash what be the expect behavior no crash which version of react and which browser os be affect by this issue do this work in previous version of react I m run react 16 12 rdt 4 2 1 11 27 2019 revision 3816ae7c3 chrome 79 0 3945 88 official build 64 bit macos catalina 10 15 2 19c57 I ve never see this crash before today interestingly the crash only happen when I select some component in the flamegraph but doesn t happen when I select other component I haven t figure out the pattern yet of which component will trigger a crash I know that this repro isn t particularly actionable at this point but I m hope that someone who know the rdt code well than I do might have an idea about why this might be happen |
facebookreact | error could not find node with i d 28540 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 47989 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 638 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 5082 in commit tree | Bug | describe what you be do when the bug occur 1 I be watch the flamegraph 2 I click on a node 3 I click on the ranked tab and the bug occur please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 436 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | devtool copy operation don t work in firefox | Bug | attempt to copy a prop use the new context menu 17608 print the follow error for firefox error unable to copy perhaps it s not available in your browser firefox itself do support document execcommand copy if it s within the context of an event handler but it look like this do not include event that originate within an extension look like this be also an issue for devtool v3 under the hood we be use clipboard js for this |
facebookreact | error could not find node with i d 479 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 52381 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | react refresh reactdom hot reloading only work when bundle react | Enhancement | do you want to request a feature or report a bug bug what be the current behavior note I be encounter this issue when use but I believe it s an issue with react refresh itself the react refresh runtime override l459 react devtool global hook inject to get a reference to the react renderer in my app the inject method be never call however because I load react react dom from a third party cdn before my application code this mean that change component be never actually refresh in the dom I believe the issue be that script be load in this order 1 react devtool set up the global hook 2 react react dom be load on the page and inject be call 3 user code which be instrument with the react refresh babel plugin be load on the page and inject be monkey patch if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below follow the usage step in the repo but also add react and react dom as external in your webpack build module export external react react react dom reactdom then load those script onto the page from a cdn e g unpkg or cdnj before the webpack bundle what be the expect behavior react refresh work the same whether react reactdom be bundle with application code or load via an external script which version of react and which browser os be affect by this issue do this work in previous version of react 16 8 6 chrome osx |
facebookreact | suspense add message when suspense promise neither resolve nor reject | Enhancement | do you want to request a feature or report a bug request a feature what be the current behavior if you throw a promise that neither resolve nor reject you hit the suspense fallback ui indefinitely and receive no console message that help you debug this which version of react and which browser os be affect by this issue do this work in previous version of react all version that allow for suspense propose feature log a warning to the console if a suspense promise take long than a certain amount of time to settle here be some code demonstrate what that could look like inside of the react codebase js try rendercomponent catch err if err err then const timeoutid settimeout console warn a suspense promise trigger in component do not resolve nor reject after 3 second if the promise never settle the suspense fallback ui will be show forever 3000 err finally cleartimeout timeoutid now actually do all the suspense magick |
facebookreact | firefox react devtool break xml formatting | Bug | step to reproduce 1 disable all add on in firefox 2 open an url that point to a xml file 3 as expect a pretty print xml be show 4 enable the react devtool add on 5 open the xml file again 6 fail only the content inside the xml tag be show use firefox developer edition 72 0b6 on macos 10 15 2 |
facebookreact | error could not find node with i d 674 in commit tree | Bug | describe what you be do when the bug occur 1 I look into a change with many commit 2 then try to navigate to the ranked tab when I see the follow error please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 44169 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 39 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 26038 in commit tree | Bug | describe what you be do when the bug occur 1 start profile record 2 click once a component some component will hide 3 stop profile record 4 click rank tab please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 5 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | bug react table element type be invalid expect a string for build in component or a class function for composite component but get undefined | Question | do you want to request a feature or report a bug bug what be the current behavior hello I be new in react and I be try to create a simple react table to display datum from db with login for user authentication until I add the login it work momentally it still throw the same mistake no matter what none of the exist solution help I I try to repair import and export I reinstall nodejs reinstall node moduls first I verify the user by log in to redirect I to the record page after verification verification be ok but then it crash if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below edit login password admin admin edit black voice 2z6y5 error message which version of react and which browser os be affect by this issue do this work in previous version of react nodejs version v8 10 0 npm version 6 13 3 ubuntu chrome please give I any advice thank you in advance |
facebookreact | error could not find node with i d 6 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 836 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 75 in commit tree | Bug | describe what you be do when the bug occur 1 start profile 2 end profile 3 iterate over commit use arrow and or bar graph please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 30 in commit tree | Bug | describe what you be do when the bug occur 1 move in next commit in profiler dev tool in ranked chart mode please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | react refresh load from cdn | Enhancement | do you want to request a feature or report a bug feature what be the current behavior when react dom be load from cdn like react refresh fail to inject hook into devtool I ve create a related issue here we should find a way to invoke injectintoglobalhook function from react refresh runtime however this file be in cjs format so we can not currently do this in a simple way what be the expect behavior I d like react refresh to publish runtime as a umd bundle so we can reference it from cdn and put it before react dom s |
facebookreact | error could not find node with i d 1758 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 275099 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 15081 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 18486 in commit tree | Bug | describe what you be do when the bug occur 1 click restart and start profile 2 finish profile 3 click on a commit and get the error below please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 490 in commit tree | Bug | I wasn t do anything too fancy run a really quick profile click on the ranked tab please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 5021 in commit tree | Bug | describe what you be do when the bug occur 1 go from flamegraph to the ranked view this doesn t reproduce consistently please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | error could not find node with i d 5203 in commit tree | Bug | describe what you be do when the bug occur 1 recording with the profiler 2 clicking on the rank chart please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc |
facebookreact | question about this state and this setstate | Question | here be my question there be a multiselect child component the value be maintain in its parent component this state value like this parent state value render return multiselect value this state value in the multiselect s onchange function I control the multiselect value in two way and two different render result first onchange this setstate value this handlevalue this state value handlevalue value here to add or splice eg value push treenode1 return value when I print this state value in the render function the treenode1 be add however ths multiselect component s treenode1 option wasn t select but if change the onchange function like this it work right onchange this setstate value this handlevalue object assign this state value I pass the copy of the this state value rather than this state value I m confused I know that we can t change varible in the state directly however in the first way this state value in the render function be add by treenode1 it look correctly here be my guess react maintain a real state when react render it can get the real state of this state value which work actually rather than the this state value that I change directly in the onchange function by add treenode1 the state value this state value print in the render function look correct because the directly change in the handlevalue function rather than change by this setstate I wonder how and why this happen and be my guess right |
facebookreact | concurrentmode suspend child alongside of input | Bug | do you want to request a feature or report a bug bug what be the current behavior after first click on button it s just fine after 3 sec after suspend mode finish when you click on button again and start type in input it will not show suspend fallback and it will wait on all 3 second seem to timeoutms be infinity now another time click on button after suspend finish this time we will not see wait phrase on button and it seem that timeoutms be zero this time what be the expect behavior show 1 5 second wait on button and after that show 1 5 second child suspend in front of it which version of react and which browser os be affect by this issue do this work in previous version of react I m use experimental version and these be new feature of concurrent mode |
facebookreact | error could not find commit datum for root 3971 and commit 3 | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162685 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332158 at sc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332375 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66573 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104884 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45721 component stack in sc in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | how do suspense and subscription interact | Question | do you want to request a feature or report a bug ask a question what be the current behavior with suspense a component throw a promise when it encounter something that s not ready however our company s datum fetching be subscription orient at a very high level the follow happen 1 component render and call usefoo i d name amount discount 2 internally the hook add a callback to the fooloader which be responsible for batch and send async request the callback will invoke the setter for a usestate inside the hook to force a rerender of the consume component 3 the hook return a remotedata which could contain the datum if it be locally available or be just a constant that say I haven t ask for this datum yet 4 when the datum become available or the request for the datum fail the fooloader invoke the hook pass in callback method which trigger the rerender which present the new component state at no point in there do the component have a promise as a result I m not sure it s possible for it to throw anything it s depend on the usestate inside usefoo to trigger rerender when datum be available but if we throw then that never happen and we wouldn t ever complete throw a promise from inside the hook doesn t seem right as it would be very difficult to combine multiple datum dependency in a single component the only alternative seem to be a pretty sizable plumbing change to return a promise instead of the loading state constant but that seem to force a lot of allocation and boilerplate code to handle the maybe not ready the first time case note post in response to this tweet by gaearon |
facebookreact | error could not find node with i d 113994 in commit tree | Bug | describe what you be do when the bug occur 1 click on rank in the profiler please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156567 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156513 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157036 at gl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314363 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 103717 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 component stack in gl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | why useeffect s default behavior be to run on every render | Question | do you want to request a feature or report a bug api design question about useeffect what be the current behavior currently useeffect run on every render this default behavior can be dangerous in situation like deal with http request when you forget to pass the second argument this seem to be a common mistake especially for newcomer like myself I can t think of many any pattern where you want to run useeffect on every render what be the reasoning behind not default to run once |
facebookreact | error could not find commit datum for root 335 and commit 2 | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162685 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332158 at sc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332375 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66573 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104884 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45721 component stack in sc in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | error getcommittree unable to reconstruct tree for root 1 and commit 21 | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150913 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 component stack in dl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | devtool highlight box be show too small | Bug | do you want to request a feature or report a bug a bug what be the current behavior when chrome devtool be highlight highlight box be show too small image what be the expect behavior highlight box be show actual template size which version of react and which browser os be affect by this issue do this work in previous version of react chrome 78 0 3904 97 react developer tool 4 2 0 |
facebookreact | why include ref as a feature seem broken and unnecessary | Question | ref never seem to work be this a break feature why not remove they and just let people use document queryselector i d action like normal people also what do this mean function component can not have ref do you mean to use react forwardref |
facebookreact | devtool resize component state prop pane | Enhancement | do you want to request a feature or report a bug I would like to request a feature what be the current behavior resize the state prop pane in component tab if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior allow resize pane which version of react and which browser os be affect by this issue do this work in previous version of react devtool 4 2 0 and chrome version 78 0 3904 97 image |
facebookreact | memoize child of suspense component doesn t update when context update | Bug | do you want to request a feature or report a bug bug I think what be the current behavior javascript const value setvalue usestate default return setvalue e target value loading when use a memoize functional component memoizedchild in above example in conjunction with context as a child of a react suspense component there seem to be a bug in which memoizedchild do not update when the context it use change for the full example see my codesandbox below in the codesandbox if you change the value of the input the new value be provide to the context which cause the hook use in memoizedchild usevalue to throw a promise this flip suspense to the fallback state and when the promise resolve memoizedchild s state be not update with the proper context value because I m assume the memoize value of memoizedchild be the one that contain the previous context value and technically no prop have change so that make sense why it wouldn t have update however this seem like it would be unexpected behavior what be the expect behavior I would expect that memoizedchild would be re render with the new provide value which version of react and which browser os be affect by this issue do this work in previous version of react I m assume all of they that contain suspense and memo so since 16 8 |
facebookreact | upgrade rollup to 0 68 1 | Bug | do you want to request a feature or report a bug bug ish what be the current behavior import react where react be the umd module build from an es module will fail due to this be not set in the context of es module so if you try to import react in that context you will get a runtime error since this be undefined and rollup before the link fix try to use this when it really mean globalthis or self if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below npm install react index html html what be the expect behavior the react umd module can be load by an es module which version of react and which browser os be affect by this issue do this work in previous version of react react 16 11 0 firefox 70 0 1 window 10 |
facebookreact | usetransition after starttransition it do not react to pass prop change | Enhancement | do you want to request a feature or report a bug probably a bug what be the current behavior after fire starttransition current component stop react to pass prop change while react to local state change if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below in the follow codesandbox count be count up in the parent component use setinterval but if we click click I it suddenly stop update what be the expect behavior when pass prop change it should show the late value of it where possible which version of react and which browser os be affect by this issue do this work in previous version of react experimental build 0 0 0 experimental 5faf377df |
facebookreact | error could not find commit datum for root 729 and commit 2 | Bug | describe what you be do when the bug occur 1 view a component within storybook 2 open profiler 3 change the target from root to story please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162685 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332158 at sc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332375 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66573 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104884 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45721 component stack in sc in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | it s confuse that usetransition doesn t do anything outside of user block event | Bug | I run into this when implement back button transition in a router because the transition be inside a browser popstate event it get batch with the low pri update and the pende state doesn t appear I have to do this l68 l69 to work around it but it s unfortunate we might want to fix this by treat pende state as special or maybe a warning but then we need a first class official api for opt into user block pri |
facebookreact | usetransition s starttransition function can result in infinite loop when it s include as a useeffect dependency | Bug | do you want to request a feature or report a bug bug what be the current behavior I ve narrow it down to this basically what I think be important be 1 there s a state change result in the useeffect be call 2 the useeffect callback start a transition 3 the transition callback set state 4 the set state result in a render which suspend if these be all the case then include the starttransition function in the dependency array will trigger an infinite loop in the codesandbox I have a safety in place so your browser doesn t fall over what be the expect behavior the starttransition function should be consistent between render I ve observe that if you do not inline the config to usetransition then this be not a problem I know that the doc recommend keep this config consistent but if this be desirable behavior then maybe a warning about this particular situation in the doc would be useful I expect that inline the config will be pretty natural for people which version of react and which browser os be affect by this issue do this work in previous version of react experimental f6b8d31a7 experimental f6b8d31a7 |
facebookreact | when call a usetransition starttransition callback outside of event handler ispending be never set to true | Bug | do you want to request a feature or report a bug bug what be the current behavior ispending be never set to true when call starttransition within useeffect but it do work properly when within a uselayouteffect here s the correct behavior accomplish via uselayouteffect good here s the incorrect behavior via useeffect bad note the difference be that the opacity never change to 0 4 which be determine base on the ispending state what be the expect behavior I expect they to both behave the same at least as far as the user can observe which version of react and which browser os be affect by this issue do this work in previous version of react experimental f6b8d31a7 experimental f6b8d31a7 |
facebookreact | static rendering strategy doesn t work on codesplitte route | Question | I m not really sure if it be a bug or not but I m face problem try to use static rendering strategy inject dom element manually to a non hydrated react component what be the expect behavior the thing that I expect to do be the next 1 render a component on server side and server it to client 2 on the head of my app have a js that will inject some dom element ad on non hydratable component 3 on client avoid hydratation of that component use the hacky thing of empty dangeroushtml what be the current behavior the thing that I expect to do be the next 1 render a component on server side and server it to client 2 on the head of my app have a js that will inject some dom element ad on non hydratable component 3 on client hydratation the code be throw a ssr vs csr missmatch and be re build everything I ve test it on page without code splitting and they seem to work like a charm only have this behavior on code splitte route what I m do wrong |
facebookreact | devtool component filter do not work with location | Question | do you want to request a feature or report a bug report a bug what be the current behavior in devtool when a component filter be add with field set to location and regex set to nothing be filter out btw no documentation in this subject be available anywhere what be the expect behavior at least some component be filter out it would also be awesome if the location be show somewhere for the select component so that user can know what kind of regex they should put together which version of react and which browser os be affect by this issue do this work in previous version of react react devtool 4 2 0 on firefox 69 0 3 |
facebookreact | miss react tab in chrome dev tool | Question | do you want to request a feature or report a bug what be the current behavior there be no react tab in my chrome dev toolbar anymore I have delete and reinstall the react extension but the issue be not resolve if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior there use to be a react tab in the chrome dev console toolbar which version of react and which browser os be affect by this issue do this work in previous version of react I m use io on google chrome |
facebookreact | blink with usetransition | Bug | bug what be the current behavior as discuss with gaearon in this thread when the usetransition be fast it result to a small blink for the user you can reproduce it in this example choose concurrent mode click next in fretch mode legacy mode a simple example can be provide but I don t have time right now I just want to track the issue what be the expect behavior the expect behaviour would be to avoid the blink if it be less than 100ms or another arbitrary delay which version of react and which browser os be affect by this issue do this work in previous version of react the experimental version see the example |
facebookreact | onmouseenter be fire on disabled button | Bug | do you want to request a feature or report a bug bug what be the current behavior onmouseenter be fire on disabled button if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior onmouseenter shouldn t be trigger on disabled button which version of react and which browser os be affect by this issue do this work in previous version of react react 16 11 0 not sure when it start to happen chrome macos |
facebookreact | eslint plugin react hook apply the rule of hook to a forwardref wrap component | Enhancement | do you want to request a feature or report a bug feature to catch potential bug what be the current behavior the react hook rule of hooks eslint rule catch use of hook in conditional in component but do not recognise an anonymous function wrap in forwardref as a component the follow example break the rule of hook but isn t catch by the rule jsx this should fail const fancybutton react forwardref prop ref if prop fancy usecustomhook return prop child what be the expect behavior the above example should be catch by react hooks rule of hook and raise the react hook usecustomhook be call conditionally error |
facebookreact | why be useeffect hook not activate when a component be reload after previously throw an error | Question | I be learn react and redux within a typescript environment I have manage to implement a container that dispatch a fetch action and subscribe to corresponding fetch success and error state notification from a redux store the source code be list below container typescript import react useeffect from react import connect from react redux import grid from material ui core grid import gridspacing from material ui core grid import course from component course course import coursemodel from redux feature course import courseselector from redux feature course import fetchcoursesasync from redux feature course action import rootstate from reduxtype type errorreport haserror boolean error error type stateprop isloade boolean course coursemodel course error errorreport redux dispatch and state mapping const dispatchprop fetchcourse fetchcoursesasync request const mapstatetoprop state rootstate stateprop isloade state course isloadingcourse course courseselector getreduxcourse state course error courseselector getreduxcourseserror state course component property type definition type prop returntype typeof dispatchprop courselist component const courselist course error fetchcourse isloade propa jsx element fetch course action on mount useeffect console log courselist fetch course fetchcourse fetchcourse if isloade return loading if error error haserror error error throw error error if throw an error then encapsulate error boundary catch and display however when the container be load again via click on a navbar link the useeffect action do not trigger alternatively if the error be render inside the container then the useeffect hook be still activate if the container be load again e g via click on a navbar link return json stringify error error null 2 return course map element export export default connect mapstatetoprop dispatchprop courselist if I throw an error within the container then the encapsulate error boundary catch and display it however when the container be reload via click on a navbar link the useeffect action do not trigger subsequently the fetchcourse action be not dispatch why be the useeffect hook not trigger on second load after it previously throw an error my errorboundary component include a home button for navigate to however after click home if I then click on link to display my courselist container the errorboundary be again display I do not see the console log message display from useeffect when navigate back to course shouldn t this recreate the courselist container be this not happen because the error be throw in render previously so the container be be reuse what be good practice for reset a component that throw an error for surround errorboundary |
facebookreact | devtool v4 be incompatible with this version of react with react native late version of react | Question | do you want to request a feature or report a bug bug what be the current behavior after start react devtool I get the follow error message devtool v4 be incompatible with this version of react either upgrade react or install react devtool v3 if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below use expo cli to initialize an expo app run yarn add react late to ensure the most recent version of react be instal currently v16 11 0 run yarn add react devtool to install react devtool run yarn start to start the app run npx react devtool to open react devtool what be the expect behavior react devtool should work with react native and the late version of react which version of react and which browser os be affect by this issue do this work in previous version of react react 16 11 0 react native 0 59 3 fedora 30 |
facebookreact | bug react devtool typeerror do not know how to serialize a bigint | Bug | what be the current behavior typeerror do not know how to serialize a bigint which make it so the react dev tool can not inspect the component prop step to reproduce 1 set a component prop to some value of type bigint 2 open chrome devtool then react component view try inspect the component 3 there will be an exception here l28 l38 with the message above you can repro this with the follow note that you need to repo via chrome devtool so that the bridge be active if you use the codesandbox build in devtool the behavior be different what be the expect behavior that bigint be handle in a similar way to how symbol be handle so that they don t crash when they cross a boundary I e postmessage which version of react and which browser os be affect by this issue do this work in previous version of react late version hasn t work before that I know test in chrome and firefox although the behavior isn t exactly the same in firefox as in chrome it doesn t appear to work in firefox either I would like to propose a fix for this but I can not find where in the source this would go I don t care for edit capability and such I just don t want the dev tool to give up on my just because I have bigint in my code |
facebookreact | utilize suspense to express app init loader | Question | with concurrent mode get finalize I go to try to solve an old problem I have the app need to run a series of init step before it can do anything viable each step depend on the previous one this be express as nest component the fairly elaborate animate logo be show for that process but it s be restart for each step and the experience be not that nice I ve prepare a demo with some experiment the first one that s active initially be what we currently have the second be what we would like to have but with less naive coding of decrease counter the last one be my attempt to use suspense but I definitely miss something out here because it behave very oddly and I can not seem to figure out why I wonder if the new usetransition should be use somehow or what s go on here |
facebookreact | error could not find node with i d 1681 in commit tree | Bug | describe what you be do when the bug occur 1 be profile component performance please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156567 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156513 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157036 at gl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314363 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 103717 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 component stack in gl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | de opt to synchronous mode in use subscription readme | Question | do you want to request a feature or report a bug outdate readme maybe what do the doc currently say use subscription be safe to use in concurrent mode however it achieve correctness by sometimes de opt to synchronous mode issuecomment 403959161 obviate the benefit of concurrent rendering in the link issue bvaughn explain issuecomment 403959161 that this be refer to chain of synchronous update use componentdidupdate however the usesubscription hook now use a passive useeffect as oppose to a synchronous componentdidupdate would this mean that it s no long de opt to sync mode and the warning could be remove from the readme |
facebookreact | eslint plugin react hook usecallback do not add dependency when callback be not function expression | Enhancement | do you want to request a feature or report a bug bug what be the current behavior when the argument of usecallback be not a function expression eslint plugin react hook will not autofix dependency example js usecallback debounce console log prop value 100 workaround js usememo debounce console log prop value 100 prop value what be the expect behavior js usecallback debounce console log prop value 100 prop value which version of react and which browser os be affect by this issue do this work in previous version of react eslint plugin react hook 1 6 0 |
facebookreact | usedeferredvalue do not abort run reconcile work for stale value | Bug | do you want to request a feature or report a bug bug what be the current behavior when usedeferredvalue value be update while the previous reconcile work be still run the previous reconcile work be not abort and the new work be queue after it repro base on usedeferredvalue example for well reproducibility I ve make it to run long use use timeoutms 30000 while performance now now 100 and I ve add an indicator value time since last key stroke start timeline record type a b c with 1 3 sec interval between key stroke see timeline there s work of 24 sec 8 8 8 for each key stroke see the value of result x change to the old stale value this be not optimal for 2 reason we show stale datum when we have something new the cpu be lock process the old value reconcile and the new value need to wait what be the expect behavior the prev reconcile work should be cancel abort and the new value reconcile should start immediately which version of react and which browser os be affect by this issue do this work in previous version of react react react dom 0 0 0 experimental 5faf377df |
facebookreact | dangerouslysetinnerhtml child and a bogus hydration warn | Bug | do you want to request a feature or report a bug bug initially report at what be the current behavior if a component have both dangerouslysetinnerhtml and child prop and the component be use with just the child prop on page load the client log a warning begin with warn prop dangerouslysetinnerhtml do not match interestingly if just dangerouslysetinnerhtml be use there be no warn multiple instance with just a child prop result in only one warning for the first occurance if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below demo in a next js project create a page with the follow content jsx const testcomponent dangerouslysetinnerhtml child export default a loading the page in a browser will result in this warning log to the console warn prop dangerouslysetinnerhtml do not match server a client note that the hydration warning be bogus use view source and the inspector you can see the ssr and client render html be identical and correct this work just the same as before but without a hydration warn jsx const testcomponent dangerouslysetinnerhtml child const divprop if dangerouslysetinnerhtml divprop dangerouslysetinnerhtml dangerouslysetinnerhtml if child divprop child child return what be the expect behavior there should be no hydration warn at first client render which version of react and which browser os be affect by this issue do this work in previous version of react not sure if the bug be present in old version of react but it can be see with v16 11 0 |
facebookreact | dom add support for the inert attribute | Bug | do you want to request a feature or report a bug feature what be the current behavior when specify inert false on an element react throw the follow message warning receive false for a non boolean attribute inert however inert undefined work fine as a replacement for false while inert empty string provide an escape hatch as a truthy value what be the expect behavior the inert attribute should be accept as a boolean dom attribute as propose inert by the html standard |
facebookreact | bail out doesn t work properly in lazy component with default prop | Bug | do you want to request a feature or report a bug bug what be the current behavior bail out doesn t work properly in lazy component with default prop it seem we re incorrectly compare unresolved prop oldprop with resolve prop newprop l1100 if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior in the example above componentdidupdate shouldn t have be call when the button be click which version of react and which browser os be affect by this issue do this work in previous version of react |
facebookreact | react devtool should produce a well error message when integer be present as key on react element | Bug | current behavior react devtool throw rangerror invalid array length when integer be use as key on react element example use anything but string as key be as far as I understand not even correct usage but it would be great if react devtool check a little bit early and have a nice error than rangeerror invalid array length it take a long time to figure out from this message that one somehow manage to use integer as key and need to correct it I ve only test with chrome and the late version of react devtool as a chrome extension |
facebookreact | error could not find node with i d 291 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156567 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 156513 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157036 at gl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314363 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66573 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104884 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 component stack in gl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | error could not find commit datum for root 226 and commit 6 | Bug | describe what you be do when the bug occur 1 record a 5 second profile in the react profiler tab 2 switch the react root in the dropdown please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162685 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332158 at sc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332375 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59263 at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66573 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104884 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89467 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89392 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86341 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45721 component stack in sc in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | weird behavior with functional component and usestate a bug or another rule | Question | react 16 9 0 sample code javascript import react from react import reactdom from react dom function optionone return blue pill const optiontwo react memo function optiontwo return red pill function app const option setoption react usestate null return setoption optionone option one setoption optiontwo option two option const rootelement document getelementbyid root reactdom render rootelement well the expect behavior be option one wasn t suppose to throw an error setstate in class component didn t mind if a key value be a pure functional component or a class component even but it seam the usestate hook be sensitive to the value pass use the setter if its another functional component it throw a confusing error bad if the pure functional component pass to setvlaue of usestate hook use hook of its own then you get multiple misleading hook error to debug so be the usestate hook work like its suppose to a rule not to pass a pure functional component as a value to the setvalue of the usestate hook or a bug |
facebookreact | can t get the profiler screenshot feature work in the react devtool | Question | I ve recently come across this tweet and see that the new devtool profiler apparently would be able to capture image of the dom after each commit and display they on the right side below the commit information be this feature indeed add to devtool 4 2 0 or be it come out in a future version just ask because I didn t manage to get it work while try with my project react 16 10 2 browser google chrome 77 0 3865 90 devtool 4 2 0 a8b8ffb89 |
facebookreact | useeffect callback never call | Bug | I want to report a bug my problem be that the callback function I pass to useeffect be never call in my app I upload a minimal app here that reproduce the issue as you can see I render a couple of nest component after the initial render I update the component state inside a useeffect callback however this callback be only execute for the first two component not for the third level component the result be that the third and subsequent level be not render at all I suspect that this be a bug in react and not a misuse on my side because do any of the follow change will let the component tree render correctly in all level don t use multiple react root if I remove the last yellow reactdom render call then the second red component tree will render correctly don t conditionally render child component remove the message default message check main tsx line 20 cause the component tree to render correctly use uselayouteffect instead of useeffect if you need additional information to reproduce the issue or have any question let I know I d like provide any help I can |
facebookreact | error could not find node with i d 952 in commit tree | Bug | describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 0 a8b8ffb89 call stack at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154414 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 at e chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154999 component stack in dl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | I be try to pass through hook effect and the code use be declare no where like chatapi | Question | js import react usestate useeffect from react function friendstatus prop const isonline setisonline usestate null function handlestatuschange status setisonline status isonline useeffect chatapi subscribetofriendstatus prop friend i d handlestatuschange return chatapi unsubscribefromfriendstatus prop friend i d handlestatuschange if isonline null return loading return isonline online offline |
facebookreact | error could not find commit datum for root 34103 and commit 1 | Bug | describe what you be do when the bug occur 1 react dev tool profiler crash when change from anonymous to overlay and ask to report the issue please do not remove the text below this line devtool version 4 1 1 a9cd9a765 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162685 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 331467 at sc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 331684 at oi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58733 at ri chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 66060 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 104557 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89163 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89088 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86037 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45275 component stack in sc in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | component not correctly display | Question | do you want to request a feature or report a bug bug what be the current behavior element not reconize if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below only use component tab in console of chrome what be the expect behavior see any element react which version of react and which browser os be affect by this issue do this work in previous version of react window 10 64bit react 16 8 1 image this be my console component visualizzation the same page visualizate with linux chrome not have any issue |
facebookreact | annoying popup from chrome devtool wrongly tell I I m use an old version of react | Bug | I be give a rather annoying popup message unsupported react version detect this version of react devtool support react dom v15 and react native v61 in order to use devtool with an old version of react you ll need to install an old version of the extension every single time I want to use devtool this be not correct I be use react 16 8 with a standard create react app build |
facebookreact | external task read non committed work in progress prop outside render phase | null | do you want to request a feature or report a bug likely a bug what be the current behavior in concurrent mode react can split render over multiple frame external task dom event handler interval perform side effect and should always access committed prop right but in the link sandbox example a schedule task use setinterval access this prop read actually the work in progress prop the issue happen with class component in render phase react mutate the prop of the class instance l1042 l1045 also the follow code indicate that the committed and work in progress fiber share the same class instance l413 if react assign pende prop to the class instance but after the render work be interrupt for some reason we yield back to the browser and we re now outside the render phase but since both the current and wip fiber share the same mutable instance this prop will continue to reflect the prop of the wip if a schedule task read this prop at this moment it ll see the wip prop while it should rather see the committed prop if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem see the example simulate some expensive work to force react to split the render work and yield back to the browser meantime a class component schedule an interval to send this prop to the external world in this case we imperatively update the content of an external dom parent prop at the top of the screen node with this prop to highlight the issue step to reproduce the issue wait for the first render to complete modify the input below app then click submit this should propagate new prop to its child component busychildren since busychildren do expensive work it ll take some time until the new prop be commit to the screen but at the same time the interval task read the pende prop before the work be commit so the top external dom node show the work in progress prop what be the expect behavior for class component this prop should return only the committed prop outside the render phase which version of react and which browser os be affect by this issue do this work in previous version of react the sandbox use the late version 16 10 0 the behavior be correct when we start in sync mode use react render |
facebookreact | profiler call onrender for component update outside of the profiler tree | Bug | from the profiler docs onrender callback the profiler require an onrender function as a prop react call this function any time a component within the profiled tree commit an update however give jsx import react from react import reactdom from react dom function counter const count setcount react usestate 0 const increment setcount c c 1 return count function app return console log call profile counter unprofiled counter reactdom render document getelementbyid root I m get a log when I click on the unprofiled counter reproduction be I misunderstand this api or be this a bug |
facebookreact | devtool extension do not show element from local file | Bug | do you want to request a feature or report a bug bug what be the current behavior when a local file be load the devtool extension display a panel in devtool but all element be miss there be no console warning or error all element display properly when use a server but the documentation say a server be not necessary in this case if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below 1 put this in index html html hello world 2 install react devtool extension and allow access to local file url 3 open index html 4 open devtool 5 open component panel what be the expect behavior hello element be display with default setting and both hello and h1 be display when the host type be not hide in setting which version of react and which browser os be affect by this issue do this work in previous version of react react reactdom 16 10 1 umd from unpkg cdn react developer tool chrome extension 4 1 2 chrome 77 0 3865 90 macos 10 14 6 |
facebookreact | error maximum call stack size exceed | Bug | describe what you be do when the bug occur 1 profile my react web page 2 3 please do not remove the text below this line devtool version 4 1 2 5184346da call stack at map have at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150140 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 at I chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 150791 component stack in dl in div in div in div in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | error minify react error in react dev tool when use component tab | Bug | do you want to request a feature or report a bug bug what be the current behavior react dev tool get this error when I try to look at the component tab if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below I don t know how to reproduce it it be work yesterday and not work today what be the expect behavior that the component tab of the react dev tool doesn t crash which version of react and which browser os be affect by this issue do this work in previous version of react 16 6 3 here be what I see it s not my react app crash it s the dev tool selection 880 copy paste of the error from the screenshot in case that s helpful the error be throw at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 61172 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 256084 at vo chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 256125 at oi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58828 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 103390 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89163 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89088 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86037 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45275 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 3691 the error occur in vo in div in aa in div in za in div in si in div in li in suspense in wa in div in div in jo in xr in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc |
facebookreact | error minify react error 301 | Bug | do you want to request a feature or report a bug bug what be the current behavior the chrome react developement tool throw this error the error be throw at hi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 61172 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 256084 at vo chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 256125 at oi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58828 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 103390 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89163 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89088 at ac chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 86037 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45275 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 3691 the error occur in vo in div in aa in div in za in div in si in div in li in suspense in wa in div in div in jo in xr in o in unknown in n in unknown in div in div in zi in ge in un in ba in rc if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below when I open the developement tool for chrome I get the error without do anythign special sometimes after reload the frame it only say unable to find react on the page I need to shutdown my whole pc and restart it then I see the tool again till I go onto the next page and it need to reaload what be the expect behavior no crash which version of react and which browser os be affect by this issue do this work in previous version of react window 10 version 1903 build 18362 356 64 bit google chrome version 77 0 3865 90 64 bit react developer tool version create from revision a9cd9a765 it work very well some day ago without any error |
facebookreact | why do parent s componentdidmount get call first then child s | Question | I think it be always the case that first child s componentdidmount would be call and then parent s however in this example first parent s componentdidmount be call then child s check the log this happen after I use this in child export default compose withstyle style withwidth child do anyone have explanation why this happen |
facebookreact | state not update in realtime | Duplicate | I be update state in setstate and the page be render correctly but react developer tool be show previous state object and array be update in realtime but not boolean string number value but when I close the dev tool window not switch tab and reopen it then only it show the update state I don t remember if this be the issue from prev version but please add realtime state update functionality to it |
facebookreact | problem with update component state in the component tab of react developer tool chrome extension | Duplicate | hello everyone I have a problem with chrome extension react developer tool if I change component s state it s not change in the dev tool window as in the screenshot below I be only able to see arrow with title reset value do somebody know how it could be fix thank a lot for help zrzut ekranu z 2019 09 25 14 06 22 |
facebookreact | react dev tool doesn t appear in chrome ubuntu 18 04 3 | Duplicate | do you want to request a feature or report a bug report a bug what be the current behavior react dev tool don t appear in chrome dev tool if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below download late chrome extension and go to open dev tool what be the expect behavior react dev tool tab should appear in chrome which version of react and which browser os be affect by this issue do this work in previous version of react react n a bash lsb release a no lsb module be available distributor i d ubuntu description ubuntu 18 04 3 lts release 18 04 codename bionic google chrome version google chrome 77 0 3865 75 this work in previous version of chrome chrome extension but I m not sure when exactly the bug surface since I haven t use it in a while thank in advance for any help react be awesome |
facebookreact | devtool hook with number string or booleans show as undefined | Bug | do you want to request a feature or report a bug report a bug what be the current behavior the usestate hook s value be show as undefined in react devtool if the value be a string or a number click on the bug icon print the correct value to console image if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react codesandbox direct link to page so you can see the devtool what be the expect behavior the devtool should show the correct value of the hook which version of react and which browser os be affect by this issue do this work in previous version of react react 16 9 0 google chrome version 77 0 3865 90 official build 64 bit run on linux x64 this issue appear after version 4 1 0 9 19 2019 of the devtool chrome extension might be same bug as 16843 but this one appear without any complicated reproduction step |
facebookreact | add displayname documentation to context | Good First Issue | do you want to request a feature or report a bug request a feature what be the current behavior no documentation be to be find on the property displayname of contexts see issuecomment 456979851 what be the expect behavior documentation on the property I want to configure the name display in react devtool of my and component but find nothing in the documentation finally find this issue and a solution issuecomment 456979851 simply add it to the documentation would be nice |
facebookreact | devtool show wrong state | Bug | do you want to request a feature or report a bug bug what be the current behavior visual bug show wrong state so user can not use devtool for debug if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below 1 open 2 open browser dev tool 3 select component click on app expand selectedpair of state 4 select 3 currency from the list on the page state be proper for now 5 uncheck any not last box devtool will remove the last from the list uncheck something once more and again just last item will disappear 6 click on bug icon log this component datum to the console expand datum state be ok so just a visual bug what be the expect behavior devtool should update state properly which version of react and which browser os be affect by this issue do this work in previous version of react react developer tool 4 1 0 9 19 2019 browser google chrome 76 0 3809 132 64bit os window 7 professional sp1 64bit |
facebookreact | devtool show only component where instead of just hide component where | Question | I wonder whether be it in the plan to do the inverse of hiding component that match the filter which be show only component where match the filter I be currently do a negative lookahead regex filter to achieve the behavior I be willing to work on it if this be a good feature to have |
facebookreact | eslint plugin react hook hook be be call conditionally error outside condition | Bug | do you want to request a feature or report a bug bug possibly what be the current behavior the plugin be show this error react hook usestate be call conditionally react hook must be call in the exact same order in every component render do you accidentally call a react hook after an early return react hook rule of hook eslint but I don t think I m call any hook conditionally the code function app prop const someobject propa true propb false for const propname in someobject if propname true console log something else console log whatever the plugin error msg on this usestate const mystate setmystate usestate null return hello codesandbox start edit to see some magic happen image what be the expect behavior the plugin wouldn t show the error in this situation which version of react and which browser os be affect by this issue do this work in previous version of react image |
facebookreact | plan for handle hide differently | Question | in one of talk about react suspense dan mention that would be deprioritize by react but still render if it have the time in his example he use it to prerender content that be seemingly part of another page however in another talk by andrew it be use to prerender tab the second showcase be incorrect accord to the living standard for this attribute the hide attribute the hidden attribute must not be use to hide content that could legitimately be show in another presentation for example it be incorrect to use hide to hide panel in a tabbed dialog because the tabbed interface be merely a kind of overflow presentation one could equally well just show all the form control in one big page with a scrollbar I don t necessarily agree with the reasoning give in the spec but I m more interested if the core team be aware of this conflict and if there be plan to resolve this somehow or simply ignore it |
facebookreact | error could not find commit datum for root 1 and commit 6 reactdevtool | Bug | react dev tool profiler describe what you be do when the bug occur be debug in storybook 1 change the value in dropdown from wrapstory to root please do not remove the text below this line devtool version 4 0 6 a39d9c3 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 11 16722 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 293893 at al chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 294128 at ha chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 55891 at bi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 62940 at xl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 99536 at hl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 84256 at fl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 81286 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 25364 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 4368 component stack in al in div in div in ir in unknown in n in unknown in div in div in wa in ce in be in so in vl |
facebookreact | wrong warning message be show | Enhancement | do you want to request a feature or report a bug bug what be the current behavior wrong warning message be show image image if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below github file github file sandbox sandbox write simple functional componenet put return method not render warning tell its render actually its not render its return method what be the expect behavior should tell its return method of something which version of react and which browser os be affect by this issue do this work in previous version of react name confusion version 0 1 0 private true dependency bootstrap 4 0 0 bootstrap social 5 1 1 cross fetch 2 1 0 font awesome 4 7 0 gh page 2 0 1 mdbreact 4 18 0 prop type 15 6 0 react 16 4 0 react animation component 3 0 0 react dom 16 4 0 react popper 0 9 2 react redux 5 0 7 react redux form 1 16 8 react router dom 4 2 2 react script 1 1 4 react transition group 2 3 0 reactstrap 5 0 0 redux 3 7 2 redux logger 3 0 6 redux thunk 2 2 0 |
facebookreact | error could not find commit datum for root 259 and commit 1 | Bug | describe what you be do when the bug occur 1 in react profiler under bar chart click one of the component 2 3 please do not remove the text below this line devtool version 4 0 6 a39d9c3 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 11 16722 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 293893 at al chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 294128 at ha chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 55891 at bi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 62940 at xl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 99536 at hl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 84256 at fl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 81286 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 43 25364 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 56 4368 component stack in al in div in div in ir in unknown in n in unknown in div in div in wa in ce in be in so in vl |
facebookreact | devtool update numeric state through incrementer decrementer doesn t render the update value | Bug | do you want to request a feature or report a bug report a bug what be the current behavior if there be a state variable that hold a number update it via incrementer decrementer doesn t render the update value in the component instead it only update if you focus click onto the field and press enter what be the expect behavior the incrementer decrementer should render the update value without have to focus onto the field and press enter which version of react and which browser os be affect by this issue do this work in previous version of react react devtool 4 0 6 browser firefox dev 70 0b6 64 bit timer state variable update the value in session hfo 19 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.