repository stringclasses 156 values | issue title stringlengths 1 1.01k ⌀ | labels stringclasses 8 values | body stringlengths 1 270k ⌀ |
|---|---|---|---|
facebookreact | devtool bug can not remove node 264 because no matching node be find in the store | Bug | website or app repro step I open chrome developer tool width react developer tool to view layout page and v while I scroll page v how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 20 0 e5f486b5a error message automate can not remove node 264 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25851 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 23957 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24117 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 52741 41 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug blank tool localhost react devtool backend js 5821 uncaught error could not find I d for fiber | Bug | website or app www google com repro step react devtool 4 20 0 react 16 8 6 not sure if relevant but react script 4 0 3 first I get an blank devtool component but when pick select element arrow and hover over element a lot of error like this one show up in the console react devtool backend js 5821 uncaught error could not find I d for fiber context provider at getfiberidthrow react devtool backend js 5821 at object getfiberidfornative react devtool backend js 7257 at overlay overlay inspect react devtool backend js 9158 at showoverlay react devtool backend js 9286 at onpointerover react devtool backend js 9445 getfiberidthrow react devtool backend js 5821 getfiberidfornative react devtool backend js 7257 inspect react devtool backend js 9158 showoverlay react devtool backend js 9286 onpointerover react devtool backend js 9445 no other error occur devtool work fine on deploy version eg work fine pr and issue that could be relate issue 22577 pr 22527 maybe relevant comment from author and maintainer of react devtool early fiber problem how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | create readme2 md | Invalid | summary how do you test this change |
facebookreact | devtool bug loading parse hook name be fail on v4 20 | Bug | website or app reactjs org repro step 1 open a website that use react 2 inspect an element that use hook 3 attempt to load hook name 4 loading hook name always fail image |
facebookreact | devtool bug blank tool localhost only | Bug | website or app google com repro step this start after last update 4 20 0 image image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug firefox and edge show error in console about unrecognized installation on v4 20 0 | Bug | website or app reactjs org repro step 1 install react devtool v4 20 0 in firefox 2 load reactjs org in firefox 3 open firefox devtool 4 observe error in console image how often do this bug happen every time |
facebookreact | devtool bug can not add node 1 because a node with that i d be already in the store | Bug | website or app how we work repro step not able to see how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 19 2 20ca9b565 error message automate can not add node 1 because a node with that i d be already in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25708 41 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 23923 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24083 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 52511 39 error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | standalone devtool splash page unresponsive after client disconnect | Bug | website or app any client that connect to the standalone devtool repro step while use the standalone devtool app 1 connect a client to the devtool 2 disconnect that client and you should be redirect to the introduction page the event listener be not re attach to the splash page element after the client disconnect the |
facebookreact | devtool bug can not add node 2934 because a node with that i d be already in the store | Bug | website or app http localhost 3000 repro step when I be use react select and dropdown I click on and before open the dropdown this error show up and react dev tool stop work how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 19 0 2178a831a error message automate can not add node 2934 because a node with that i d be already in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25701 41 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 23916 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24076 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 52332 39 error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | react 18 | Invalid | null |
facebookreact | devtool bug could not inspect element with i d 2 error throw cache datum for element 2 not find | Bug | website or app server public deploy3 test eu tankionline com config xml resource resource balancer repro step attempt to change the line of the code which lock the store in an online game this usually work but this time it didn t how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 18 0 f58bbcf9a error message automate could not inspect element with i d 2 error throw cache datum for element 2 not find error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37563 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36542 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 38972 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34323 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34764 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40911 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36249 5 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at schedulingprofilercontextcontroll chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 42093 3 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40537 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29185 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29796 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36605 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 51354 3 github query string automate text not inspect element with i d error throw cache datum for element not find in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 15 error throw cache datum for element 15 not find | Bug | website or app repro step cd repo and then start the server use npm start in browser mozilla firefox when I try to add the user and age and try to debug the output in listuser component I m face this error screenshot from 2021 10 01 18 52 36 how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 19 0 2178a831a error message automate could not inspect element with i d 15 error throw cache datum for element 15 not find error call stack automate no response error component stack automate text inspectedelementcontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 38121 43 suspense errorboundary errorboundary moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36518 5 div inspectedelementerrorboundarywrapper moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36967 46 nativestylecontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 39541 38 div div ownerslistcontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 34741 37 settingsmodalcontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 35182 40 component component moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 41481 52 errorboundary errorboundary moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36518 5 div div themeprovider moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36635 23 portaledcontent moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36669 34 div div div themeprovider moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 36635 23 schedulingprofilercontextcontroll moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 42673 45 profilercontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 41106 35 treecontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 29603 31 settingscontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 30214 35 modaldialogcontextcontroller moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 37030 38 devtool devtool moz extension 8a220e8e c7fe 42e7 9ec5 0b6e67ae5dd5 build main js 52130 27 github query string automate text not inspect element with i d error throw cache datum for element not find in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug setstate updater call but not render in safari in concurrent mode | Bug | react version 18 0 0 alpha 9175f4d15 20210928 step to reproduce minimal reproduction in this codesandbox this issue only appear in safari include mobile safari it work fine in chrome and firefox in order to reproduce you ll need to 0 render the app with createroot in the late 18 0 alpha 1 within an element s ref function append an iframe to that element use appendchild the follow step have be remove after simplify the reproduction 1 make a state change originate in a message from a youtube embed iframe I assume the same issue would occur with message from other cross domain iframe although I have not test this the issue do not appear when make an async state change through settimeout 2 render a tooltip use the tippy js library I haven t dig into what inside of tippy be cause this but comment out the tippy element resolve the issue I have confirm that render a simple portal do not reproduce the issue link to code example the current behavior in the example in safari the updater function pass to setstate be run confirm with the run state updater console log but the new state be never pass to the component function leave the app hang with no error message and display not do the expect behavior in chrome and firefox the app component update after the state updater function be call as expect display do thank for all the wonderful work on react btw it s be a lot of fun playing with the new concurrent react feature can t wait to see they hit a stable release |
facebookreact | devtool bug emoji as visual helper produce strange symbole | Bug | website or app repro step emoji seem support but produce strange symbole image to test emoji on window os use win how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | bug component inside typescript namespace cause referenceerror | Bug | forward from by not rusty base on the recommendation of sodatea which state that this should be consider as a bug in the react refresh package describe the bug apparently component inside namespace be not support I don t exactly know if the error come from esbuild or something but it would nice the bug be that be not show as a compilation error reproduction simply start a react ts project with npm init vitejs app my vue app template react ts and write the follow code ts namespace lol export const lol return some component function app return hello vite react export default app system info js system os linux 5 8 ubuntu 20 04 2 lts focal fossa cpu 8 x64 intel r core tm i5 10210u cpu 1 60ghz memory 440 54 mb 7 47 gb container yes shell 5 8 usr bin zsh binarie node 14 16 0 usr local bin node npm 6 14 13 usr local bin npm browser chrome 90 0 4430 93 firefox 89 0 1 use package manager npm log I get the following runtime error js app tsx 13 uncaught referenceerror c be not define at app tsx 13 at app tsx 14 I suppose it should be a compilation error |
facebookreact | devtool bug emoji seem support but produce strange symbole | Bug | website or app repro step emoji seem support but produce strange symbole image very low priority maybe because it affect nothing how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | error can not read property length of undefined | Bug | describe what you be do when the bug occur 1 just try to profile an react native app screenshot 2021 09 16 07 44 35 please do not remove the text below this line devtool version 4 10 1 3a8c04e3b2 call stack at jc nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 342921 at ii nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 59391 at kl nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 114564 at ns nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 101189 at be nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 101117 at os nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 100980 at gs nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 24 96690 at w nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 40 1749 at messageport a port1 onmessage nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 40 2251 component stack at jc nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 341665 at div at div at fi nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 235808 at nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 347533 at hi nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 249715 at nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 251980 at div at div at lu nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 305412 at en nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 173743 at jn nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 184811 at ji nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 253490 at nd nix store dhc43b6q83i2d842ry36ydnwck64wlyc react native debugger 0 11 7 share resource app asar node modules react devtool core dist standalone js 56 353738 |
facebookreact | devtool bug hook parse fail with fetch error | Bug | website or app repro step have a webpack project that use a domain map to your local ip such as appx whenidev net in my case that s serve with https try to resolve hook name check console and observe the million error show my console how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug hook resolution throw fetch failure | Bug | website or app n a repro step have a webpack project that use a domain map to your local ip such as appx whenidev net in my case that s serve with https try to resolve hook name check console and observe the million error show my console how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool backend console setting reportedly not sync to rn backend | Bug | feedthejim report that disable the break on warning feature do not update the backend setting in memory without a reload for react native screen shoot 2021 09 14 at 11 07 04 am I believe the new setting should be update here l133 l138 but it sound like they aren t we should investigate |
facebookreact | bug maximum call stack size exceed react devtool | Bug | I encounter the same issue as 20640 but use react devtool as a stand alone app instead of from the the browser the bottom line be that the profiler become unresponsive after any interaction with a heavily load react page react version react 17 0 2 reactdom 17 0 2 react devtool 4 18 0 step to reproduce 1 attach a react devtool stand alone yarn run react devtool to a session 2 start profile 3 do something on your app that would cause a huge number of update 4 the profiler stop function diagnostic I actually go through and find out the origin of the issue however I be not sure what would be the good approach to fix it it seem the the origin be a very big incoming message that eventually cause a maximum call stack exceed error come from util js 128 ts export function utfdecodestre array array string return string fromcodepoint array and interestingly enough do spread operator with an array with 235124 element actually cause a maximum call stack size exceed error I try replace the code above with the follow replacement and it seem to work ts export function utfdecodestre array array string return array map c string fromcodepoint c join |
facebookreact | devtool bug could not inspect element with i d 28 error throw cache datum for element 28 not find | Bug | website or app website url localhost repro step click the reload devtool button to turn devtool in light mode devtool be already in light mode how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 18 0 f58bbcf9a error message automate could not inspect element with i d 28 error throw cache datum for element 28 not find error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37563 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36542 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 38972 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34323 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34764 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40911 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36249 5 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at schedulingprofilercontextcontroll chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 42093 3 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40537 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29185 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29796 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36605 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 51354 3 github query string automate text not inspect element with i d error throw cache datum for element not find in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool support provide the number of component above select or depth | Bug | website or app context while implement appium e2e test we find this limitation I m try to figure out how to solve this and understand if my change be reduce the number of layer above a certain component how often do this bug happen sometimes devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug could not inspect element with i d 219 error throw cache datum for element 219 not find | Bug | website or app employer test apna co repro step the error occur at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37563 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36542 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 38972 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34323 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34764 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40911 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36249 5 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at schedulingprofilercontextcontroll chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 42093 3 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40537 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29185 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29796 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36605 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 51354 3 how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 18 0 f58bbcf9a error message automate could not inspect element with i d 219 error throw cache datum for element 219 not find error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37563 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36542 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 38972 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34323 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34764 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40911 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36097 5 at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36249 5 at div at div at div at themeprovider chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36215 3 at schedulingprofilercontextcontroll chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 42093 3 at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40537 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29185 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29796 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36605 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 51354 3 github query string automate text not inspect element with i d error throw cache datum for element not find in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug useeffect not trigger on dep change | Bug | I stumble upon this issue which I believe be react bug even though I find it use react query minimal project be create to demonstrate the problem in card status js I register useeffect which be watch for certain change and it just display the message whenever dep change the problem be that one state change get swallow by useeffect it can be see if you click on a button and watch the console useeffect be not trigger even though ui update correctly aka rerender be trigger I have find that the issue be cause by line 60 in the same file image if that line be comment out then useeffect trigger properly when button be click also if setstate on line 60 be call with number for example then it also behave correctly I believe this be a react issue react version 17 0 2 step to reproduce 1 open the console and click on the activate trial button 2 useeffect message be not visible upon click even though dependency change and ui be rerendere link to code example codesandbox github repo tosheen use effect bug git the current behavior useeffect do not register that the dependency have change the expect behavior useeffect should register new change since every other part of the ui do |
facebookreact | bug can not set property memoizedstate of null | Duplicate | do you want to request a feature or report a bug a bug what be the current behavior can not set property memoizedstate of null 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 const processlink html return rendertostaticmarkup const richtext html const htmlprocesse usememo processlink html html see what be the expect behavior which version of react and which browser os be affect by this issue do this work in previous version of react the current behavior the expect behavior |
facebookreact | devtool bug flamegraph section overflow and not resizable | Bug | website or app any site repro step I have a page that have lot of component so the component tree be pretty long when I profile on it the flamechart just overflow by default and I have to put it fullscreen to see the why do this render side bar image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug context usecontext some child component don t rerender but highlight | Bug | website or app repro step bug desc context usecontext some child component don t rerender but highlight 1 open react devtool 2 image open highlight 3 click app button and watch highlight image 4 the child1 component don t usecontext and don t rerender but highlight when child2 update context image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug profiler freeze when navigate through commit | Bug | website or app repro step 1 enable chrome flag enable throttle display none and visibility hidden cross origin iframe 1 goto continuousslider 1 record at least 2 commit via profiler the large the component tree the more reliable the crash when I reduce the component tree in the ui the crash stop at some point how often do this bug happen every time devtool package automate 1d2528097 devtool version automate 4 16 error message automate no response error call stack automate no response error component stack automate no response github query string automate text profiler freeze |
facebookreact | react dom alpha umd bundle throw when render | Bug | react version 18 0 0 alpha bd255700d 20210816 or main branch step to reproduce 1 use reactdom development from alpha version or main branch 2 call reactdom render or reactdom createroot render link to code example if you open devtool you can see the error which be prevent render if you change the script from development js to production min js you can see the problem go away |
facebookreact | devtool bug could not inspect element with i d 1335 | Bug | website or app web app we be develop for a client repro step open the component tab no component will display close the component tab open the component tab again this time the the component show but the error show on the right pane how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 1335 error call stack automate no response error component stack automate text 109842 43 suspense 108452 5 div 108838 46 111206 38 div div 106680 37 107121 40 113123 52 108452 5 108571 34 div div 112748 35 103336 31 103939 35 108901 38 115897 27 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 3 | Bug | website or app code repro step pure project with command npx create react app use npm template typescript then run and open react devtool the follow message appeard how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 15 0 c6f2188ed error message automate could not inspect element with i d 3 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller testerrorstack js 143043 3 at suspense at errorboundary errorboundary testerrorstack js 141591 5 at div at inspectedelementerrorboundarywrapper testerrorstack js 142024 3 at nativestylecontextcontroller testerrorstack js 144425 3 at div at div at ownerslistcontextcontroller testerrorstack js 139820 3 at settingsmodalcontextcontroller testerrorstack js 140261 3 at component component testerrorstack js 146350 52 at errorboundary errorboundary testerrorstack js 141591 5 at div at div at themeprovider testerrorstack js 141709 3 at portaledcontent testerrorstack js 141743 5 at div at div at div at themeprovider testerrorstack js 141709 3 at schedulingprofilercontextcontroll testerrorstack js 147386 3 at profilercontextcontroller testerrorstack js 145976 3 at treecontextcontroller testerrorstack js 134687 3 at settingscontextcontroller testerrorstack js 135298 3 at modaldialogcontextcontroller testerrorstack js 142087 3 at devtool devtool testerrorstack js 156036 3 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 7 | Bug | website or app localhost repro step I m do a chat app use graphql along with reactjs I use contextapi to get the user login bearer token throughout the app this issue occur when I want to check the context value to be sure for the token receive how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 7 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller testerrorstack js 109843 3 at suspense at errorboundary errorboundary testerrorstack js 108452 5 at div at inspectedelementerrorboundarywrapper testerrorstack js 108839 3 at nativestylecontextcontroller testerrorstack js 111207 3 at div at div at ownerslistcontextcontroller testerrorstack js 106681 3 at settingsmodalcontextcontroller testerrorstack js 107122 3 at component component testerrorstack js 113123 52 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug | Bug | website or app repro step I ve reproduce this with brave and chrome 1 login with your own facebook account 2 open the react devtool 3 notice the scrollable component be squish to one side image seem to not happen to everyone but quite a few other have see this happen and I can t figure out what s cause this how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | bug html doesn t work with muted attribute | Duplicate | when try to embed a video you can use the html tag for some reason if you put the muted attribute on it it win t stick to the dom which doesn t allow video to autoplay what make it difficult with privacy setting of a couple of browser like safari on io so here be a proof I notice it after a couple of test on io for I the muted tag wasn t important for play video on chrome on io the video just autoplay when the muted tag be set img 20210808 103818 my research have show that the bug have exist since 2016 fix just for now but not practically let s use dangerouslysetinnerhtml to ensure the muted attribute be write to the dom 1 hewat2uh6mghjvbcqoylma 1 |
facebookreact | devtool bug getcommittree invalid commit 12 for root 1 there be only 12 commit | Bug | website or app website repro step multiple click on next step how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate getcommittree invalid commit 12 for root 1 there be only 12 commit error call stack automate text at getcommittree testerrorstack js 98337 11 at profilingcache profilingcache getcommittree testerrorstack js 98872 11 at commitflamegraphautosizer testerrorstack js 113938 33 at oh testerrorstack js 57941 7 at gi testerrorstack js 58719 7 at vk testerrorstack js 61516 86 at uk testerrorstack js 61037 11 at tk testerrorstack js 61029 23 at lk testerrorstack js 61013 5 at dk testerrorstack js 60719 28 error component stack automate text at commitflamegraphautosizer testerrorstack js 113921 34 at div at div at div at settingsmodalcontextcontroller testerrorstack js 107122 3 at profiler profiler testerrorstack js 115395 34 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text invalid commit for root there be only commit in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug createportal anywhere in the tree make native event be run too late | Duplicate | summary native event add via useeffect be call too late and with improper new state rather than the state during listener attachment if there s a reactdom createportal anywhere in the tree first the effect be re run and a new listener be attach and only then the native event be call react version 17 0 2 link to code example codesandbox reproduction anywhere in the tree be a createportal it can even be createportal null document body somewhere there be a component with usestate it render a div the div have an onclick handler pass on top of that useeffect be use to attach a click event to window both event handler both the native event attach to window and the react event pass to div use setstate the current behavior the react handler be call it call setstate the component rerender with the new state and its effect be re run since the effect be re run a new native listener be attach which be bind to the new state only then the new listener with the new state be call the expect behavior the react handler be call it call setstate the component might rerender or not doesn t matter the native handler be call with the old state in other word const popupopen setpopupopen usestate false useeffect close popup if click anywhere on the screen some code ignore for brevity const listener console log native popupopen if popupopen setpopupopen false window addeventlistener click listener return window removeeventlistener click listener popupopen return console log react popupopen react handler state if popupopen setpopupopen true open popup reactdom createportal null document body log image but without createportal the follow be log image |
facebookreact | devtool bug component tree size too small component can t be select | Bug | website or app repro step 1 visit reactjs org 2 open devtool 3 open component tab at first the component tree win t appear once I m at the component tab I then have to also refresh the page to make the tree render and when it do render it still doesn t work properly as a note this issue start happen after I have to forcibly restart my computer since then I have try reinstall the extension restart chrome restart my pc all of which haven t work I d like to avoid reinstall chrome completely but that s the only thing I haven t yet try use window 10 btw here be what the broken component tree look like it s very narrow and the component can not be select tree how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug commit tree do not contain fiber 191 this be a bug in react devtool | Bug | website or app localhost 3000 repro step when I be in profiler and then I be click how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate commit tree do not contain fiber 191 this be a bug in react devtool error call stack automate text at updatetree testerrorstack js 98499 21 at getcommittree testerrorstack js 98365 20 at profilingcache profilingcache getcommittree testerrorstack js 98872 11 at commitflamegraphautosizer testerrorstack js 113938 33 at oh testerrorstack js 57941 7 at gi testerrorstack js 58719 7 at vk testerrorstack js 61516 86 at uk testerrorstack js 61037 11 at tk testerrorstack js 61029 23 at lk testerrorstack js 61013 5 error component stack automate text at commitflamegraphautosizer testerrorstack js 113921 34 at div at div at div at settingsmodalcontextcontroller testerrorstack js 107122 3 at profiler profiler testerrorstack js 115395 34 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text tree do not contain fiber this be a bug in react devtool in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 333 | Bug | website or app repro step f12 how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 333 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller testerrorstack js 109843 3 at suspense at errorboundary errorboundary testerrorstack js 108452 5 at div at inspectedelementerrorboundarywrapper testerrorstack js 108839 3 at nativestylecontextcontroller testerrorstack js 111207 3 at div at div at ownerslistcontextcontroller testerrorstack js 106681 3 at settingsmodalcontextcontroller testerrorstack js 107122 3 at component component testerrorstack js 113123 52 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug strictmode not show in component tree | Bug | website or app repro step open react devtool in codesandbox see that there s no strictmode in the tree any more how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug could not inspect element with i d 18 | Bug | website or app localhost repro step enable dev tool and click on component tab how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 18 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller testerrorstack js 109843 3 at suspense at errorboundary errorboundary testerrorstack js 108452 5 at div at inspectedelementerrorboundarywrapper testerrorstack js 108839 3 at nativestylecontextcontroller testerrorstack js 111207 3 at div at div at ownerslistcontextcontroller testerrorstack js 106681 3 at settingsmodalcontextcontroller testerrorstack js 107122 3 at component component testerrorstack js 113123 52 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 175 | Bug | website or app localhost 4000 repro step just simple react app how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 175 error call stack automate no response error component stack automate text 109842 43 suspense 108452 5 div 108838 46 111206 38 div div 106680 37 107121 40 113123 52 108452 5 108571 34 div div 112748 35 103336 31 103939 35 108901 38 115897 27 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 3824 | Bug | website or app local website repro step open some component that use the hook usequery of react query package how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate could not inspect element with i d 3824 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller testerrorstack js 109843 3 at suspense at errorboundary errorboundary testerrorstack js 108452 5 at div at inspectedelementerrorboundarywrapper testerrorstack js 108839 3 at nativestylecontextcontroller testerrorstack js 111207 3 at div at div at ownerslistcontextcontroller testerrorstack js 106681 3 at settingsmodalcontextcontroller testerrorstack js 107122 3 at component component testerrorstack js 113123 52 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text not inspect element with i d in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug commit tree do not contain fiber 1422 this be a bug in react devtool | Bug | website or app localhost 3000 repro step the bug appear during the usage of react dev profiler tool while call a route through react router dom mypwa zip how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 14 0 d0ec283819 error message automate commit tree do not contain fiber 1422 this be a bug in react devtool error call stack automate text at updatetree testerrorstack js 98499 21 at getcommittree testerrorstack js 98365 20 at profilingcache profilingcache getcommittree testerrorstack js 98872 11 at commitflamegraphautosizer testerrorstack js 113938 33 at oh testerrorstack js 57941 7 at gi testerrorstack js 58719 7 at vk testerrorstack js 61516 86 at uk testerrorstack js 61037 11 at tk testerrorstack js 61029 23 at lk testerrorstack js 61013 5 error component stack automate text at commitflamegraphautosizer testerrorstack js 113921 34 at div at div at div at settingsmodalcontextcontroller testerrorstack js 107122 3 at profiler profiler testerrorstack js 115395 34 at errorboundary errorboundary testerrorstack js 108452 5 at portaledcontent testerrorstack js 108572 5 at div at div at profilercontextcontroller testerrorstack js 112749 3 at treecontextcontroller testerrorstack js 103337 3 at settingscontextcontroller testerrorstack js 103940 3 at modaldialogcontextcontroller testerrorstack js 108902 3 at devtool devtool testerrorstack js 115898 3 github query string automate text tree do not contain fiber this be a bug in react devtool in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug highlight update when component render | Bug | website or app repro step I switch on highlight update when component render use memo with function component but when main element of component be fragment extension doesn t show highlight but when I change to another element for example div highlight be occurs but console doesn t show that child component be reload how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | highlight update when component render | Bug | website or app repro step I switch on highlight update when component render use memo with function component but when main element of component be fragment extension doesn t show highlight but when I change to another element for example div highlight be occurs but console doesn t show that child component be reload how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | react developer tool | Question | I successfully instal the extension but I be not able to see the the news tab component and react |
facebookreact | react 18 usestate share state value between component of the same type | Question | I create a custom table component that have pagination search bar and export to excel button the main usage of the component be as follow jsx to enable pagination global filter and dataset download I use state variable use usestate hook as follow jsx const clientstable prop let dataset header pagesize action identifier downloadfilename prop const displaydataset setdisplaydataset usestate dataset const pageindex setpageindex usestate 0 const numpage math ceil displaydataset length pagesize const cannextpage setcannextpage usestate true const canprevpage setcanprevpage usestate false const sortsmalltolarge setsortsmalltolarge usestate true const sortingfield setsortingfield usestate null some logic for filter pagination and render render only one table component in an app view work just fine however render two or more implie that react use the same state variable for all table component in the view this be unintended behavior for I in particular I create a custom tab component that render two different table on tab selection the two table have the same state variable different pro though which cause conflict in the view how can I render multiple table component in my app without have this behavior thank in advance |
facebookreact | devtool name hook transient error | Bug | sometimes name hook inspection will seemingly fail the first time then work the second time e g use a dev build of facebook com the component currently do this I think this might indicate a timeout during inspection so the retry be fast because everything be cache |
facebookreact | react 17 bug click event be pick up by component render by the click | Duplicate | react version 17 2 step to reproduce 1 use a class component if a click event change some state which render a new component and the new component add an event listener on its componentdidmount check for click the new component will trigger that event link to code example this do not happen if the create component use hook to add its event listener the current behavior a state change via a click that cause a new component to be render that new component can pick up the original click event that create it which seem like its reach back in time to so speak the expect behavior perhaps this be now intend behavior with the react 17 event change although it doesn t happen if I add the event listener with a hook on a functional component but I would expect that if a click event cause a render and the listener be add on the componentdidmount function I would assume the click be complete and wouldn t be detect |
facebookreact | devtool bug could not inspect element with i d 192 | Bug | website or app website for development repro step uncaught error could not inspect element with i d 192 how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 192 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 192 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug commit tree do not contain fiber 266 this be a bug in react devtool | Bug | website or app repro step 1 login with number how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate commit tree do not contain fiber 266 this be a bug in react devtool error call stack automate text at updatetree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 20110 21 at getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19976 20 at profilingcache profilingcache getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 20483 11 at commitflamegraphautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 35327 33 at oh chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 13163 7 at zi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 13864 7 at sk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16652 86 at rk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16172 11 at qk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16164 23 at hk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16148 5 error component stack automate text at commitflamegraphautosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 35310 34 at div at div at div at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at profiler profiler chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 36739 34 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text tree do not contain fiber this be a bug in react devtool in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with I d 3 | Bug | website or app chorme repro step 1 compile my react app 2 the bug happend how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 3 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 3 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug extension not show on browser | Bug | I have instal react dev tool extension but can t see it in the inspect window |
facebookreact | devtool bug can not add child 11802 to parent 11726 because parent node be not find in the store | Bug | website or app repro step the error be throw at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21126 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 how often do this bug happen sometimes devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not add child 11802 to parent 11726 because parent node be not find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21126 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate text the error be throw at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21126 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 github query string automate text add child to parent because parent node be not find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not remove node 2862 because no matching node be find in the store | Bug | website or app website repro step when I open the dev tool in chrome it s will see every time how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not remove node 2862 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21178 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not remove node 30123 because no matching node be find in the store | Bug | website or app repro step 1 go to this getstream io demo app 2 open react dev tool 3 send a message in the app 4 error how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not remove node 30123 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21178 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 3903 | Bug | website or app my local site repro step 1 log in 2 inspect an element how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 3903 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 3903 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 4 | Bug | website or app repro step I be use hook for make an control input I don treally know how it happend sorry how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with I d 4 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with I d 4 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug setting panel layout break | Bug | website or app repro step website be actually irrelevant but require 1 open the devtool 2 press the setting button 3 observe the layout be break cause horizontal scrollbar screenshot image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug indentation break for component tab | Bug | website or app repro step 1 make sure the devtool be narrow but still wide enough that its panel remain side by side 2 drag the splitter between the panel 3 observe the indentation change with the width of the component tree panel the effect be not super effective on the give website but on the development version the component name be quite a bit long and so it seem to depend on the length of component name how far the indentation be this be weird and unneccesary please change it so that the indentation be fix how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug where s the error stack trace | Bug | website or app there s no error stack trace when there s an error repro step there s no error stack trace when there s an error how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool bug long key overlap | Bug | website or app repro step image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | bug layout effect don t re fire in 18 on suspense re show | Bug | intend behavior sandbox expect when suspend content be hide and then show we get layout cleanup follow by layout setup actual only layout cleanup happen |
facebookreact | devtool bug could not inspect element with i d 38 | Bug | website or app I be use local host repro step I be add redux devtool how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 38 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 38 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with I d 649 | Bug | website or app my localhost repro step 1 inspect the page 2 select column of the display table 3 click on empty cache and hard reload how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 649 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 649 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug crash when inspect component use a hook that return a proxy | Bug | website or app repro step provide be a code sandbox with a very simplified version of the code which trigger this bug 1 open the code sandbox app in a new window 2 open developer tool 3 select the component tab 4 click on the app component observe that devtool crash and the console print out an error similar to this uncaught typeerror symbol iterator return a non object value formatdataforpreview moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 849 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1718 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1769 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1767 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1702 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1702 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1769 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1767 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1702 dehydrate moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1702 cleanforbridge moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 1195 inspectelement moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 7827 agent agent moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 9561 emit moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 4175 wallunlisten moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10201 listener moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10975 addeventlistener eval 4 listen moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10978 bridge moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10200 setup moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10968 welcome moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10947 addeventlistener eval 4 moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 10950 webpack require moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 20 moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 84 moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build react devtool backend js 87 react devtool b this happen in both firefox and chrome how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 2 error call stack automate no response error component stack automate text inspectedelementcontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 31391 43 suspense errorboundary errorboundary moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 30033 5 div inspectedelementerrorboundarywrapper moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 30175 46 nativestylecontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 32660 38 div div ownerslistcontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 28267 37 settingsmodalcontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 28708 40 component component moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 34512 52 errorboundary errorboundary moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 30033 5 portaledcontent moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 30146 34 div div profilercontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 34137 35 treecontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 24944 31 settingscontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 25547 35 modaldialogcontextcontroller moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 30233 38 devtool devtool moz extension 739d174b 7aaa 4387 b750 af9bc181bf82 build main js 37240 27 github query string automate text not inspect element with i d 2 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not remove node 5 because no matching node be find in the store | Bug | website or app repro step this bug be show when I be reload the page it will be very helpful if someone provide I with a solution how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not remove node 5 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21178 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | question starttransition behavior | Question | I m very sorry that I m use the issue tracker to ask this question but I think other might ask the same question after read I don t have comment right js function handleinputchange e const input e target value setinputvalue input starttransition setsearchquery input what happen if the user type ab I e js pseudocode represent the first event handler trigger by keystroke a setinputvalue a starttransition setsearchquery a pseudocode represent the second event handler trigger by keystroke b setinputvalue ab starttransition setsearchquery ab from my understanding setinputvalue a and setinputvalue ab will batch generate a single rerender the callback setsearchquery a pass to the first starttransition will be cancel and only the second callback setsearchquery ab pass to the second starttransition will be execute I e js pseudocode represent the final logic after keystroke a and b setinputvalue a will batch with setinputvalue ab starttransition setsearchquery a noop this callback will be cancel setinputvalue ab starttransition setsearchquery ab be I correct I think this question be important because if the first callback pass to starttransition really get cancel and I try to do more work inside it I should have in mind that the additional work will not happen cc gaearon acdlite |
facebookreact | devtool bug can not add node 1 because a node with that i d be already in the store | Bug | website or app localshost repro step load react app in development mode use webpack the redux devtool show error message as above how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not add node 1 because a node with that i d be already in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21069 41 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not add node 476 because a node with that i d be already in the store | Bug | website or app repro step 1 load page 2 open react component 3 click button for unfold all list how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not add node 476 because a node with that i d be already in the store error call stack automate no response error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with I d 5 | Bug | website or app react create app example repro step 1 react 17 0 2 react dom 17 0 2 2 code example import react component fragment from react class todolist extend component constructor prop super prop this state value list handleclickbtn this setstate value list this state list this state value handledel idx const list this state list slice 0 list splice idx 1 this setstate list handleinput e this setstate value e target value render return this state list map v idx return v this handledel idx export default todolist how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 5 error call stack automate text report this issue please include step on how to reproduce it and the component use uncaught error could not inspect element with i d 5 dismiss the error occur at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with I d 5 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug setstate run twice with own hook | Question | react version 17 0 2 step to reproduce 1 click app 2 link to code example js const usel service const l setl usestate const ab setab usestate const load async const re await service setab t log twice console log 22222 setl l re l return t useeffect load return list l load export default function app const a seta usestate const load usel return new promise re settimeout seta 1 re l 1 2 2000 const handle load return handle hello codesandbox start edit to see some magic happen why log twice edit by bvaughn to fix format |
facebookreact | bug react hook exhaustive dep false positive with direct function call on an object | Duplicate | eslint plugin react hook version 4 2 0 when call a function within useeffect where the function exist directly on an object and the function be include in the effect s dependency array the react hook exhaustive dep eslint rule be trigger I m wonder whether this be a false positive or if there be actually a valid reason for this eslint rule to be trigger in this scenario please let I know if this have already be answer explain elsewhere I try search for this problem and couldn t find anything about it it s also worth note that I find this out when try to call react query usemutation mutateasync within a useeffect call as the return value of usemutation be not referentially stable include the whole object in the dependency array isn t feasible as it cause the effect to fire more than it should however as mention in that link issue the function object on the return object be referentially stable which mean that include x mutateasync where x be assign the return value of the usemutation call in the dependency array mean that the effect fire only when it actually need to should do however when try to do so react hook exhaustive dep return the warning mention I understand that I could get around this warning by destructure the mutateasync off of the return object before use it in useeffect but that would be bad dx wise in my opinion and I d like to avoid it if possible step to reproduce 1 call a function within useeffect where the function exist directly on an object and include the function in the effect s dependency array 2 see the eslint warning come from react hook exhaustive dep link to code example the above example show the follow scenario to show that the behavior feel inconsistent and potentially wrong 1 call a function within useeffect where the function exist directly on an object the case in question 2 call a function within useeffect where the function do exist on an object but be call from a different variable 3 reference another value in this case a number within useeffect where the value exist directly on an object the current behavior the react hook exhaustive dep rule return the follow warning in the case in the code example above react hook react useeffect have a miss dependency test either include it or remove the dependency array the expect behavior no warning come from react hook exhaustive dep or an explanation be give by the rule as to why this be a problem |
facebookreact | devtool bug could not inspect element with I d 2 | Bug | website or app private code repro step not interact with browser how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 2 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 2 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with I d 2 | Bug | website or app repro step how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 2 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with i d 2 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with I d 4 | Bug | website or app react repro step just work on a side project in react use redux and middleware how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with I d 4 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with I d 4 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 10 | Bug | website or app repro step 1 git clone cd hook todo 2 npm I npm run dev 3 open in chrome if it wasn t open automatically 4 open devtool 5 go to source tab and enable the pause on exception icon 6 go to component tab the tab of react devtool 7 click in the component tree on the component todolist image the source tab show that local variable visibletodo which be an array have the numeric value 0 or 1 image the error message on the screenshot be typeerror visibletodo map be not a function its stack trace todolist todolist js 90 l react devtool backend js 12276 export inspecthooksoffiber react devtool backend js 12342 inspectelementraw react devtool backend js 7562 inspectelement react devtool backend js 7807 anonymous react devtool backend js 9561 emit react devtool backend js 4175 anonymous react devtool backend js 10201 listener react devtool backend js 10975 postmessage async handlemessagefromdevtool contentscript js 107 do not reproduce in production e g at the error arise only in dev build how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with i d 10 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with I d 10 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug could not inspect element with i d 9 | Bug | website or app repro step develop a simple react app in a course on udemy 1 this be the link address 2 how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate could not inspect element with I d 9 error call stack automate no response error component stack automate text at inspectedelementcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 31392 3 at suspense at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at div at inspectedelementerrorboundarywrapper chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30176 3 at nativestylecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32661 3 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28268 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28709 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34512 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30033 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30147 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34138 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24945 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25548 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30234 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37241 3 github query string automate text not inspect element with I d 9 in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not remove node 47636 because no matching node be find in the store | Bug | website or app development server localhost 3000 repro step 1 open component tab 2 update node tree how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 5 0ae5290b54 error message automate can not remove node 47636 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21178 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not remove node 96 because no matching node be find in the store | Bug | website or app not sure I can share work code here repro step this seem to happen when hide a loading component after a successful api request how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 4 51ebccc374 error message automate can not remove node 96 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21178 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19286 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19446 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37413 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | remove debugid field from fiber | Good First Issue | this dev only field be add in 836331ba5f69f2cc53b273ec073fae116db14302 by sebmarkbage but it s not be use anymore to my knowledge |
facebookreact | bug yarn test not work after fresh installation | Duplicate | hello follow your documentation send a pull request I make a fresh install and the test be fail even before do any modification to the repository react version the one on master branch commit ubuntu lts node v14 16 1 step to reproduce 1 git clone 2 yarn install 3 yarn test link to code example I do not do anything yet and I receive 3 error screenshot from 2021 05 22 23 05 59 screenshot from 2021 05 22 23 06 17 screenshot from 2021 05 22 23 06 21 screenshot from 2021 05 22 23 06 24 the current behavior the test be fail the expect behavior the test should pass after a fresh install |
facebookreact | devtool bug can not add node 1 because a node with that i d be already in the store | Bug | website or app repro step 1 use react storybook 2 right click element in website 2 click inspect 3 go to react dev tool component tab 4 tab be blank then error appear how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 13 4 51ebccc374 error message automate can not add node 1 because a node with that i d be already in the store error call stack automate no response error component stack automate no response github query string automate text add node because a node with that i d be already in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug can not read property iscollapse of undefined | Bug | website or app chrome repro step 1 open react devtool 2 select the component tab 3 get below error how often do this bug happen only once devtool package automate react devtool extension devtool version automate 4 13 3 d6604ac031 error message automate can not read property iscollapse of undefined error call stack automate text at store store getelementatindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21750 35 at store store getelementidatindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21766 26 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29360 63 at list render chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 23484 18 at fi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 13922 76 at ei chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 13913 10 at sk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16655 86 at rk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16172 11 at qk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16164 23 at hk chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 16148 5 error component stack automate text at list chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 23179 30 at div at autosizer chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 3642 5 at div at div at tree tree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 29121 47 at div at div at ownerslistcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28270 3 at settingsmodalcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 28711 3 at component component chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34555 52 at errorboundary errorboundary chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30035 5 at portaledcontent chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30136 5 at div at div at profilercontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 34181 3 at treecontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 24947 3 at settingscontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 25550 3 at modaldialogcontextcontroller chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 30277 3 at devtool devtool chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37284 3 github query string automate text read property iscollapse of undefined in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug react memo cause devtool to fail to render the entire dom tree | Bug | website or app company website repro step 1 the devtool fail to render the entire tree therefore I could not find any element to debug within the devtool 2 we target it down to the use of react memo to wrap one of our component 3 when remove the react memo logic everything work as expect how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | devtool error can not remove node 2315 because no matching node be find in the store | Bug | website or app website repro step not sure how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 13 2 e468072e17 error message automate can not remove node 2315 because no matching node be find in the store error call stack automate no response error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug onclick handler not call on mobile safari iphone | Bug | react version 17 0 2 step to reproduce 1 add onclick event to any element 2 test that onclick be work on mobile device link to code example the current behavior onclick event be not fire on mobile device I already try the cursor pointer fix but it be still not work the expect behavior onclick event should get fire on all device |
facebookreact | devtool error can not remove node 145 because no matching node be find in the store | Bug | website or app repro step after login with email and password and the validation from the server this happen when I try to redirect to the home page how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 2 e468072e17 error message automate can not remove node 145 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21477 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19585 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19745 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37733 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug fast refresh devtool break component inspection | Bug | website or app repro step 1 yarn start 2 open app js 3 uncomment the useeffect block 4 click to inspect component in devtool 5 error could not inspect element with I d 5 originally report in issuecomment 835406075 how often do this bug happen every time |
facebookreact | devtool error can not remove node 527 because no matching node be find in the store | Bug | website or app localhost repro step the error be throw at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21477 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19585 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19745 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37733 39 how often do this bug happen often devtool package automate react devtool extension devtool version automate 4 13 2 e468072e17 error message automate can not remove node 527 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21477 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19585 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19745 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37733 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | bug where do the component tree go in the new version | Bug | website or app repro step in this image below I can t seem to find the old component tree it use to be in this empty upper half now all I can see it render by so be it remove or be there something wrong with my extension image how often do this bug happen every time devtool package automate no response devtool version automate no response error message automate no response error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | experimental createroot method not available in react 17 | Question | I be use react and react dom v17 0 2 and I be try to use the unstable createroot method to render my app but look like that method be not even present in react v17 0 2 can someone comment if this be expect or not thank arpit |
facebookreact | devtool error can not remove node 771 because no matching node be find in the store | Bug | website or app repro step I m use a context to manage app global state like in website when get that error how often do this bug happen every time devtool package automate react devtool extension devtool version automate 4 13 2 e468072e17 error message automate can not remove node 771 because no matching node be find in the store error call stack automate text at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21477 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19585 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19745 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37733 39 error component stack automate no response github query string automate text remove node because no matching node be find in the store in title be issue be open be public label component developer tool repo facebook react |
facebookreact | devtool bug console log throw type error if one of the argument be symbol | Bug | website or app l199 repro step this function will throw this error if one of the argument be type of symbol the error be swallow here l194 l196 but it do interfere with debugging when I run with the pause on catch exception I get trap here all the time can we change js if args length format args join update escape value into js for let I 0 I args length I format string args I update escape value how often do this bug happen every time devtool package automate no response devtool version automate 4 13 2 e468072e17 error message automate typeerror can not convert a symbol value to a string error call stack automate no response error component stack automate no response github query string automate no response |
facebookreact | bug apply an invalid style will use property from previous render | Duplicate | apply an invalid style will use property from previous render this can cause some hard to pin down bug since you may inadvertently be apply invalid style but not notice because the style on the previous render be fine but then render later on with the same prop state will cause a different style to be apply because of what happen on the previous render react version 17 0 2 step to reproduce 1 apply a valid style property to a component e g backgroundcolor red 2 apply an invalid style property to a component for example backgroundcolor 5 3 note background stay red 4 change state to apply a valid style or no style e g backgroundcolor white 5 note background be now white 6 change state to apply an invalid style again 7 note that the background stay white even though it have the same prop as step 2 when it render red link to code example click change then clear then change again to see it in action the current behaviour when a style object property be invalid it apply style property from the previous render the expect behaviour I think the sensible thing to do would be display a warning in development mode if a property be invalid remove any the previous style property from the element if the property pass be invalid however I think as long as it do the same thing regardless of prop pass in the previous render it be acceptable |
facebookreact | bug effect be run on parent of suspend component | Duplicate | with a component hierarchy like tsx this one suspend if the child throw to suspense neither the parent nor child be in the dom however the parent effect be still run this break class of layout effect e g measure text etc react version 17 0 2 step to reproduce 1 open code sandbox 2 look at console link to code example see the console the current behavior effect be run on parent component even though it isn t in the dom the expect behavior effect be not run on the parent component until it be actually mount |
facebookreact | error can not read property length of undefined | Bug | describe what you be do when the bug occur 1 profiler button click 2 profiler use for 5 sec 3 profiler button stop click and immediately this error please do not remove the text below this line devtool version 4 12 4 7becb2ff1b call stack at ec application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 329422 at fi application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 63339 at as application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 119731 at ps application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 105351 at rs application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 105279 at fs application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 105142 at ws application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 101735 at ho application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 47259 at application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 110813 at ms application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 110819 at ds application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 101335 at ws application react native debugger app content resources app asar node modules react devtool core dist standalone js 24 101866 at w application react native debugger app content resources app asar node modules react devtool core dist standalone js 40 1739 at immediate a as onimmediate application react native debugger app content resources app asar node modules react devtool core dist standalone js 40 2098 at processimmediate internal timer js 439 21 component stack at ec application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 327171 at div at div at ja application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 235611 at application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 334153 at hi application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 247849 at application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 248684 at div at div at cs application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 295413 at hn application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 180675 at un application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 194758 at ii application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 250120 at nc application react native debugger app content resources app asar node modules react devtool core dist standalone js 56 338247 |
facebookreact | error can not remove node 1105 because no matching node be find in the store | Bug | which website or app be you use when the bug happen please provide a link to the url of the website if it be public a codesandbox example that reproduce the bug or a project on github that we can checkout and run locally what be you do on the website or app when the bug happen if possible please describe how to reproduce this bug on the website or app mention above 1 2 3 generate information devtool version 4 13 1 93782cfed2 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 21499 43 at bridge bridge emit chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19607 22 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 19767 12 at listener chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 37788 39 component stack none github url search query |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.