repository
stringclasses
156 values
issue title
stringlengths
1
1.01k
labels
stringclasses
8 values
body
stringlengths
1
270k
facebookreact
bug react lazy throw undefined instead of an error object
Bug
react version 16 13 1 step to reproduce js import react suspense lazy from react const async lazy let app return export default app link to code example might be relate to context I know that this be incorrect code but lazy import be a rather easy typo to make the main reason why I m bring this be up be that other tool like jsdom and codesandbox with the link above expect an error object to be throw the current behavior input const async lazy async error this be correct warn lazy expect the result of a dynamic import call instead receive object object your code should look like const mycomponent lazy import mycomponent input const async lazy error the exception be not an error object uncaught input const async lazy error the exception be not an error object uncaught undefined the expect behavior input const async lazy async error warn lazy expect the result of a dynamic import call instead receive object object your code should look like const mycomponent lazy import mycomponent input const async lazy error warn lazy expect the result of a dynamic import call instead receive undefined your code should look like const mycomponent lazy import mycomponent input const async lazy error warn lazy expect the result of a dynamic import call instead receive object object your code should look like const mycomponent lazy import mycomponent
facebookreact
error commit tree do not contain fiber 3204 this be a bug in react devtool
Bug
when I try to navigate in commit react dev tool profiler I get this error commit tree do not contain fiber 8562 screen shoot 2020 04 27 at 12 00 23 devtool version 4 6 0 6cceaeb67 component stack in ec in div in div in div in so in unknown in n in unknown in div in div in rl in ze in fn in ga in s
facebookreact
react hook will render multiple time after await
Question
const html sethtml usestate const script setscript usestate const update script html setscript script sethtml html update a b the above code work fine react hook will render once and combine setscript sethtml const html sethtml usestate const script setscript usestate const update async script html await new promise resolve settimeout resolve 10 setscript script sethtml html update a b the above code doesn t work anymore react hook will render twice and it doesn t combine setscript sethtml I can change to the code to const state setstate usestate html script const update async script html await new promise resolve settimeout resolve 10 setstate script html update a b the above code only render once but it have a new bug the cursor in the textarea where script and html go will move to the end of the textarea instead of stay at where it be
facebookreact
error commit tree do not contain fiber 55875 this be a bug in react devtool
Bug
describe what you be do when the bug occur 1 profile my session then select to show commit over 10ms 2 go through commit in profiler please do not remove the text below this line devtool version 4 6 0 6cceaeb67 call stack at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 162825 at n chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 161772 at e getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 164582 at ec chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 339280 at ci chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59620 at nl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 69923 at ll chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 110996 at qc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 102381 at hc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 102306 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 102171 component stack in ec in div in div in div in so in unknown in n in unknown in div in div in rl in ze in fn in ga in s
facebookreact
bug function component can not have ref property
Question
when pass ref property to a function component validatefunctioncomponentindev show a warning about it be a bad thing react version head while this might have be true for stateless function component as many place refer to func component probably since the introduction of hook they can have state and I have the impression that one could rewrite any class component into a function base one function testcomponent ref const state react usestate statefield1 42 assignref ref state return state statefield1 this code will not work caller would never be able to get the answer caller be sad the current behavior react give a warning and make the ref prop defunct the expect behavior remove limitation and let ref on my function component live happily ever after
facebookreact
bug normal update between idle render and a ping cause fallback to get stick
Bug
repro case with a master build expect we see content after a second actual fallback never resolve this happen in a sequence of 1 normal update which suspend 2 idle update which also suspend 3 an unrelated normal update immediately follow by a ping so they re batch here we decide to stay on fallback but should ve show the content if you remove setversion v v 1 on line 44 then the issue go away
facebookreact
bug idle update may cause normal priority update to get stick
Bug
this repro be quite convoluted but it s the good I could extract it seem like numerous thing need to happen to trigger this bug to reproduce 1 open and wait a second 3 observe that there be only one hello for ub normal update get stick 4 also notice how clicking wake up which schedule a dummy update will let the other update come through you may need to tweak the timing of cpuspin component if this doesn t repro for you
facebookreact
bug devtool should grab native settimeout
Enhancement
just notice this I think we should read settimeout early in devtool because we don t want the overridden one that go through indirection
facebookreact
delay set usetransition ispende to true until jnd
Enhancement
do you want to request a feature or report a bug maybe a feature when use suspense and usetransition the ispending of usetransition be immediately set to true I want to show a spinner when a transition be still pende but show it immediately result in a flash spinner when the underlying promise resolve very fast this be not a nice experience be there a usetransition suspense option to delay the ispende indicator I want to prevent the spinner from show if the transition complete in for example 100ms
facebookreact
bug bubble onfocus handler that trigger an update prevent onchange handler in createroot
Bug
react version I think any experimental version test use 0 0 0 experimental 5faf377df and 0 0 0 experimental e5d06e34b at least step to reproduce 1 open codesandbox 2 attempt to click on the label text for the checkbox in the createroot section 3 notice that the checkbox win t check onchange isn t call 2 attempt to click on the label text for the checkbox in the render section 3 notice that the checkbox will check onchange be call link to code example the current behavior when render use createroot onfocus be call onchange be not call when render use render onfocus be call onchange be call my coworker and I spend a bit of time debug this if we at all schedule the onfocus setstate handler use settimeout or requestanimationframe for example then onchange be always call from the input e g jsx handlefocus settimeout this setstate ishovere true 0 or requestanimationframe this setstate ishovere true additionally if the label be a sibling to the input jsx return label text then the onchange handler will be call as well note onfocus win t be call in this case because there isn t a focusable element within it also worth note re implement the checkbox component use hook will still run into the same bug no difference between use class vs hook the expect behavior call setstate in onfocus shouldn t prevent onchange on a nest input element to be call both onfocus and onchange should be call
facebookreact
devtool memo forwardref and render by list
Enhancement
if you have memo forwardref x then the inner component win t have a render by list this be because it technically doesn t have an owner it be artificial I think we should ideally set up debugowner for these fiber in dev just so exist tooling can find they or special case they in devtool
facebookreact
bug devtool in firefox do not allow add prop or edit prop state hook
Bug
version react 16 13 1 firefox 75 0 version for manjaro linux devtool version 4 6 0 6cceaeb67 important I have the same react devtool version 4 6 0 6cceaeb67 instal in google chrome beta 81 and it s work as expect step to reproduce 1 open react devtool component tab 2 select a component with prop state 3 try to add prop or edit prop state or hook here s a screen grab of the issue react devtool issue between the click I m type on my keyboard but nothing happen the current behavior all key type in this tab be ignore the expect behavior I should be able to add prop or alter prop state hook etc
facebookreact
bug devtool search filtering remove a space
Bug
compare two screenshot closely the space after from disappear when the next word be select
facebookreact
bug dev tool typeerror can not read property memoizedstate of null
Bug
react version step to reproduce repro step use confidential internal fb tool provide separately gist of the repro 1 open app 2 open react dev tool to profile tab 3 turn on record why each component render while profile 4 interact with app 5 follow error occur typeerror can not read property memoizedstate of null 6 inspect the flamegraph now show incomplete information base on the stack trace it look like the issue occur specifically on this line l135
facebookreact
bug drop update when render phase update happen before suspend
Bug
sandbox repro type a and then after a second b expect eventually you ll see ab in all field pende indicator go away actual you ll keep see a in low pri field pende indicator be stick
facebookreact
extention react non d finie sur chrome
Question
react developer tool 4 6 0 google chrome version 80 0 3987 149 l outil de d veloppement react est inactif sur la console google chrome
facebookreact
style box transform scale this state scalenum scale scalenum scalenum
Question
scale scalenum scalenum
facebookreact
bug suspense fallback potentially never show due to a race
Bug
see I haven t verify but it seem plausible
facebookreact
bug suspenselist revealorder together and error boundary
Bug
react version 0 0 0 experimental aae83a4b9 step to reproduce 1 wrap and error boundary around a suspense boundary inside a 2 crash with can not read property share of null link to code example be fork from the current behavior the follow code cause the describe crash jsx loading post loading fun fact revealorder forwards do not crash as well as place the error boundary inside the suspense boundary like so jsx loading post loading fun fact the expect behavior the position of the errorboundary be likely wrong in the first place since I can move it around to not cause a crash while preserve the semantic I expect maybe this need a descriptive warning error why this be happen and how I should resolve it
facebookreact
call all function twice in strictmode
Enhancement
react version 16 3 16 13 step to reproduce 1 render function component with side effect and without hook in strictmode 2 component only render once link to code example the current behavior strictmode only render function component with hook twice follow issuecomment 471197572 the expect behavior I think make the distinction between component with and without hook cause more confusion than it help especially since the doc do not mention this I amend past effort to improve the strictmode doc but since this have be ignore I m not sure this help I would also work on make the behavior consistent across all function component type if this be possible
facebookreact
error could not find commit datum for root 220 and commit 65
Bug
describe what you be do when the bug occur 1 change root of flamegraph from a react one to image please do not remove the text below this line devtool version 4 5 0 355970aa4 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 171903 at p chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 358164 at zc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 358379 at ti chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58696 at qi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 67715 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108833 at jc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 100072 at oc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99997 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99862 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96528 component stack in zc in div in div in so in unknown in n in unknown in div in div in rl in ze in fn in ga in s
facebookreact
bug high pri setstate cause primary tree to get unhidden
Bug
repro notice the flash I d expect suspend to be true during the high pri render
facebookreact
bug update in the primary tree only unsuspend once
Bug
1 press suspend see loading 2 wait five second you ll see happy birthday at some point 3 you win t see it again no matter how long you wait expect you ll see it every five second
facebookreact
error can not read property concat of undefined
Bug
describe what you be do when the bug occur 1 I be use the devtool to investigate some performance issue w an app I help maintain 2 I have just turn on the record why each component render while profile checkbox 3 I run a profile while navigate on the underlying page the react profiler tab in the devtool give this error I think as I click the record icon to stop record the profile please do not remove the text below this line devtool version 4 5 0 355970aa4 call stack at n chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160881 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160015 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 at j chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159939 component stack in ec in div in div in div in so in unknown in n in unknown in div in div in rl in ze in fn in ga in s
facebookreact
bug eslint plugin react hook recommend config rule do not work
Bug
since the late plugin version 2 5 0 there should be a recommend config for eslint plugin react hook see pr 14762 unfortunately this config do not work I be pretty sure the bundled index js do not include the expect code eslint version 6 8 0 eslint plugin react hook version 2 5 0 step to reproduce link to code example the current behavior oop something go wrong eslint 6 8 0 eslint couldn t find the config plugin react hook recommend to extend from please check that the name of the config be correct the config plugin react hook recommend be reference from the config file in projectdir eslint plugin react hook err eslintrc json if you still have problem please stop by to chat with the team error command fail with exit code 2 info visit for documentation about this command the expect behavior yarn exit code 0
facebookreact
bug sync mode effect be not re run after suspense complete
null
as report in 14536 react mount suspend component to the dom with display none and fire effect before the component be visible once suspense have complete effect be not re run this mean that any component that read layout info from the dom become visible with content base on a stale layout react version 16 12 0 step to reproduce 1 create a component that read layout info from the dom 2 render that component in a suspense alongside a lazy component link to code example the current behavior the layout dependent component be render incorrectly base on when it be still invisible the expect behavior the layout dependent component should render correctly regardless of whether or not sibling be lazy and cause suspense
facebookreact
bug input win t trigger onchange after a chain of setstate
Bug
react dom version 16 9 0 to 16 12 0 late this bug be not present in 16 8 6 step to reproduce 1 create a control input element 2 add an onkeydown event handler that will change a state 3 add a useeffect hook that depend on the state from 2 and change another state 4 try to type in something in the input link to code example the current behavior the input update with the key the user have press the expect behavior the input doesn t update the handler for onkeydown be call but the handler for onchange wasn t
facebookreact
bug eslint plugin react hook in comment the version notation be break
Bug
at cjs eslint plugin react hooks development js and cjs eslint plugin react hook production min js the version notation in the comment be break v2 3 0 be ok not fatal but could be a bug the current behavior js license react vundefine the expect behavior js license react v2 4 0
facebookreact
question why not usecallback always return static value without dep
Question
tsx function userefcallback void callback t const ref useref callback ref current callback return usecallback function this any args parameter return ref current apply this args as t I think userefcallback be safe to replace usecallback in any code and it s well than usecallback because it will never cause recalculation
facebookreact
question it s not problem just question in my mind
Question
why all implement of hook in react dom and we have to import from react just I want to know about it
facebookreact
question how to remove dynamic child from parent state
Question
I m use react hook usecontext I have two identical component sibling each that use the same context that be a list scenario 1 the first sibling be create call usecontext and then push something into the list 2 the second sibling be then create use the same usecontext and then push something into the list issue the second sibling have the current state of list which have two item but the first sibling state be not update with the second item that be push in by the second sibling expect that each component that be use the same usecontext will be update amongst all component that use the same context be this a bug or be I misuse this any help or guidance be appreciate
facebookreact
doc spanish translation error
Invalid
this issue tracker be not for documentation issue within the the datum flow down section there be an error on the spanish version where it would be correct to say pueden saber si un determinado componente tiene o no estado y no les deber a importar instead of pueden saber si un determinado componente tiene o no tiene estado y no les deber a importar
facebookreact
devtool profiler getcommittree unable to reconstruct tree for root and commit
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 4 0 f749045a5 call stack at n chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 154255 at e getcommittree chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157019 at yl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 320890 at ei chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58864 at mi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 67500 at yl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108161 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99474 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99399 at fc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96173 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 45937 component stack in yl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
question how to use useref when it be pass through portal
Question
hi I create ref in root component in my app when I bind ref to element which be a child of another element that be render in the portal ref current property be always undefined sandbox with example here how can I use ref with portal with expect behaviour
facebookreact
displayname from memoize component should be take into account in devtool
Bug
if you create a component via react memo and then explicitly provide it with a displayname devtool ignore this display name react version 16 12 0 devtool version 4 4 0 step to reproduce 1 create a component like tsx const fancymemocomponent react memo check my name in devtool 2 provide it with a displayname tsx fancymemocomponent displayname fancymemocomponent 3 check its name in devtool link to code example the current behavior devtool do not display the give displayname the expect behavior devtool should display the give displayname comment I be aware that the name can be pick from the function inside react memo but I prefer use anonymous function I be use this workaround tsx fancymemocomponent type displayname fancymemocomponent
facebookreact
bug event preventdefault be wreck havoc with starttransition
Bug
react version 241c446 step to reproduce 1 click show a to render the lazy component 2 type into the input whose placeholder say it work starttransition will call inline loading will show for 2 second then the suspense boundary will trigger 3 click the update button same as above everything work 4 now type into the input whose placeholder say it doesn t work note that the inline placeholder stay up for the entire time the suspense boundary never show 5 now note that step 2 or 3 will likely immediately show the suspense boundary the bypass rendering of the suspense boundary from step 4 seem to be back up stuck somewhere and be now unleash note that step 2 and 3 be optional no matter what the preventdefault that s call in step 4 cause this incorrect behavior no matter whether step 2 or 3 have be exercise link to code example see above the current behavior starttransition should suspend after the timeout even if event preventdefault be call the expect behavior it do not
facebookreact
devtool profiler could not find commit datum for root
Bug
the devtool profiler occasionally encounter the error could not find commit datum for root and commit this issue be intermittent and we do not currently know hot to reproduce it if you can reproduce it we would love to get any of the follow information from you info about how you reproduce it share your code or site with we an export profiler json that contain the bug this may be less useful since the bug likely happen pre export but may still be helpful
facebookreact
bug usetransition s pende boolean be trigger immediately even if there s no suspension
Enhancement
react version 241c4467e step to reproduce 1 2 swap between the two screen by click the two button 3 inline loading show the first time you load screen a but it also usually show on subsequent load even though there s nothing suspend link to code example the current behavior inline loading indicator usually show on subsequent load the expect behavior it should only show on the first load of a
facebookreact
webpack can t find reactdom createroot
Question
hi I m kinda in doubt if this be an error or be just I do something wrong I be try the new react experimental in a very simple exist app I have although I have instal the react experimental version in my package json it seem it doesn t recognize reactdom createroot when I try to run my project I receive the error message from the console uncaught typeerror react dom webpack import module 1 default a createroot be not a function at module src client index js main chunk js 2437 at webpack require runtime bundle js 786 at fn runtime bundle js 151 at object 0 main chunk js 4324 at webpack require runtime bundle js 786 at checkdeferredmodule runtime bundle js 46 at array webpackjsonpcallback as push runtime bundle js 33 at main chunk js 1 this only happen when I try use reactdom createroot use reactdom render everything work perfectly any idea why this be happen dependency chalk 3 0 0 compression 1 7 4 express 4 17 1 morgan 1 9 1 uuid 3 4 0 devdependencie babel cli 7 8 4 babel core 7 8 4 babel node 7 8 4 babel plugin proposal class property 7 7 4 babel plugin proposal decorator 7 7 4 babel plugin proposal export namespace from 7 7 4 babel plugin proposal function bind 7 7 4 babel plugin proposal nullish coalescing operator 7 7 4 babel plugin proposal optional chain 7 7 5 babel plugin proposal pipeline operator 7 7 7 babel plugin proposal private method 7 7 4 babel plugin proposal throw expression 7 7 4 babel plugin syntax dynamic import 7 7 4 babel preset env 7 8 4 babel preset react 7 7 4 babel preset typescript 7 8 3 hot loader react dom 16 11 0 testing library jest dom 5 1 1 testing library react 9 4 0 autoprefixer 9 7 4 babel eslint 11 0 0 beta 2 babel jest 25 1 0 babel loader 8 0 6 babel plugin dynamic import node 2 3 0 babel plugin style component 1 10 7 case sensitive path webpack plugin 2 3 0 circular dependency plugin 5 2 0 clean webpack plugin 3 0 0 connect react router 6 6 1 copy webpack plugin 5 1 1 core js 3 6 2 css hot loader 1 4 4 css loader 3 4 1 deep freeze 0 0 1 eslint 6 8 0 eslint loader 3 0 3 eslint plugin babel 5 3 0 eslint plugin import 2 20 1 eslint plugin jsx a11y 6 2 3 eslint plugin ramda 2 5 1 eslint plugin react 7 18 3 eslint plugin react hook 2 3 0 eslint plugin redux saga 1 1 3 eslint watch 6 0 1 file loader 5 0 2 hard source webpack plugin 0 13 1 history 4 10 1 html webpack plugin 3 2 0 immer 5 3 4 jest 25 1 0 jest style component 7 0 0 lodash 4 17 15 mini css extract plugin 0 9 0 moment 2 24 0 nock 11 7 1 normalizr 3 5 0 npm run all 4 1 5 open 7 0 2 optimize css asset webpack plugin 5 0 3 pm2 4 2 3 postcss flexbug fix 4 2 0 postcss loader 3 0 0 prop type 15 7 2 ramda 0 27 0 react 0 0 0 experimental 241c4467e react dom 0 0 0 experimental 241c4467e react hook test library 0 6 0 react hot loader 4 12 19 react be 16 12 0 react redux 7 1 3 react router 5 1 2 react router dom 5 1 2 react test renderer 16 12 0 redux 4 0 5 redux action 2 6 5 redux devtool extension 2 13 8 redux logger 3 0 6 redux saga 1 1 3 redux saga test plan 4 0 0 rc 3 regenerator runtime 0 13 3 reselect 4 0 0 source map loader 0 2 4 style loader 1 1 3 style component 5 0 1 stylelint 13 0 0 stylelint bare webpack plugin 2 0 0 stylelint config recommend 3 0 0 stylelint config standard 19 0 0 stylelint config style component 0 1 1 stylelint custom processor loader 0 6 0 stylelint order 4 0 0 stylelint processor style component 1 9 0 stylelint selector bem pattern 2 1 0 thread loader 2 1 3 typescript 3 7 5 url loader 3 0 0 webpack 4 41 4 webpack dev middleware 3 7 2 webpack hot middleware 2 25 0 webpack manifest plugin 2 2 0 webpack merge 4 2 2 webpack pwa manifest 4 1 1 workbox webpack plugin 5 0 0
facebookreact
question can I lie to useeffect about its dependency in this case
Question
you frequently 1 see 2 warning that you shouldn t lie to useeffect and usememo about their dependency I m wonder about this special case which I see throughout the codebase at work useeffect we want effect to run when a change but not b dostuff a b a let s say a change every 10 second and b change every second and we want to dostuff whenever a change this work be simple and elegant yet all guide discourage this suggest to do this instead let bref useref useeffect bref current b useeffect dostuff a bref current a why aren t those equivalent I could see a potential issue with usememo compute a b a it can be access in the entire component and sometimes it will be stale which contradict the meaning of memoization but what about that useeffect case 1 do not lie to react about dependency 2 be it safe to omit function from the list of dependency
facebookreact
bug nest setstate and unstable batchedupdate be they ignore
Question
nest setstate and unstable batchedupdate be they ignore react version 16 12 step to reproduce open profile after click you will see 3 commit it seem that even if we use unstable batchedupdate nest setstate call on didupdate layouteffect do not get batch
facebookreact
question can usememo be use instead of useref
Question
hi just out of curiosity can usememo be use instead of useref when do it as follow example javascript const ref useref null const ref2 usememo current null it look to I that both ref will be work just fine as dom ref and as mutable value similar to instance field in class why then useref be implement differently compare to usememo consider reactfiberhook js code for useref and usememo thank
facebookreact
while use useref some datum have be update by context value from reducer when the context value be update from some other user event variable use with useref also update then how to use instance variable in hook
Question
const createnotificationbase prop const state dispatch usecontext store const draftdata useref useeffect if state notificationdetail draftid draftdata current state notificationdetail useeffect debugger draftdata current when value in store context change useeffect of draftdata current also call please suggest hwo to resolve
facebookreact
bug react devtool profiler doesn t show prop
Question
accord to doc it s possible to see prop and state of a component at each commit browse commit yet in every project I ve try all I see be the name of change prop but not their value like the gif from docs claim react version 16 12 0 extension 4 4 0 1 3 2020 create from revision f749045a5 on 1 3 2020 step to reproduce 1 create counter app with cra or another method 2 open profiler and change state 3 observe how only the name of the prop be visible but not its value function app let a seta usestate 0 return seta v v 1 inc function kid return null the current behavior current behavior the expect behavior expect behavior be I do something wrong or have this feature be remove I know you can see prop in the inspector but there it s only the most recent one
facebookreact
doc
Invalid
this issue tracker be not for documentation issue the react website be host on a separate repository you may let the team know about any issue with the documentation by open an issue there
facebookreact
bug usereducer run the queue update with new prop
Bug
react version 16 8 0 step to reproduce link to code example link to codesandbox the current behavior initially step be 0 so for every step react do not rerender due to this l1347 but state update be queue so when step change all the state update be do and hence create a bug by add the new step prop why usereducer be the cheat mode of hook
facebookreact
passive effect destroy and create function be interleave
Bug
we currently run all passive destroy function for an individual fiber before run passive create function what we should be do be run all passive destroy function for all fiber before run any passive create function like we do for layout effect the reason this be important be that interleave destroy create effect between sible component might cause component to interfere with each other e g a destroy function in one component may unintentionally override a ref value set by a create function in another component we handle this for layout effect by invoke all destroy function during the mutation phase and all create function during the layout phase but for passive effect we call both in a single traversal l394 l409 fix this probably mean split our passive effect loop into two pass l2179 l2222 however this could be a break change since it would affect time so we should probably do it behind a feature flag for now also note that split this into two pass could have another unintended effect an error throw in a passive destroy function would no long prevent subsequent create function from be run on that fiber as be currently the case unless we add code to handle that specific case we should decide what the expect behavior be here
facebookreact
bug excessive cpu usage of the page when react devtool be active
Bug
when option highlight update when component render be activate the whole page repaint in rapid succession after the component state have be change it cause 100 cpu usage by the browser and unpleasant dx due low fps react version 16 12 0 devtool version 4 4 0 f749045a5 the sequance of action be important 1 open react application 2 open react devtool 3 check option highlight update when component render in react devtool setting 4 change the internal state of a component 5 in activity monitor there will be 100 cpu usage of the page or check option paint flash in render pane of chrome devtool image image the code example to trigger the issue 1 check the option highlight update when component render and 2 click on the button import react usestate from react function app const count setcount usestate 0 return setcount count 1 click count export default app the current behavior excessive cpu usage of the page the expect behavior normal cpu usage of the page
facebookreact
question just for my app test thank
Question
this issue tracker be not for question as it happen support request that be create as issue be likely to be close we want to make sure you be able to find the help you seek please take a look at the follow resource code question if you have a code question relate to react and react dom it might be well suit for stack overflow it s a great place to browse through frequent question about use react as well as ask for help with specific question talk to other react developer there be many online forum which be a great place for discussion about good practice and application architecture as well as the future of react popular discussion forum proposal if you d like to discuss topic relate to the future of react or would like to propose a new feature or change before send a pull request please check out the discussion and proposal repository
facebookreact
bug infinite loop when a set state hook be call in a global handler
Bug
to be honest I be not 100 sure it s a bug perhaps my code be badly write but I don t know why it s not work or how to rewrite it in the proper way react version 16 12 0 step to reproduce function hello const s set react usestate 1 const print set s 1 settimeout window print 600 window onafterprint set s 1 return s print 1 open this jsfiddle or try the code above 2 click print button and cancel the print dialog link to code example the current behavior when the set be call in the onafterprint handler the app enter an infinite loop with 100 cpu usage so you win t be able to do anything on the page the profiler show that it happen inside react the expect behavior the set successfully modify the state and the component re render browser version 79 0 3945 130 official build 64 bit
facebookreact
question can the usecontext hook be use without a provider
Question
be it a correct form to use the usecontext hook without the enclose provider see this simple sandbox which use the jedicontext provider in this modify sandbox I remove the provider and the usecontext hook still work what be the consequence of use the usecontext hook without a provider
facebookreact
bug event from an in the of a disabled get supresse
Bug
the close relate issue I could be somewhat of the inverse of this one 7711 react version 16 12 old version as well step to reproduce 1 create a component 2 add state indicate whether it be enable or disabled advise to start as enable 3 on render let the component return a with a contain an checkbox element and another form element 4 add the disabled attribute that follow the aforementioned state to the 5 make the onchange event of the in the responsible for modify the state of the component enable disabled 6 run an app that use the describe component 7 disable the use the in its 8 try to enable the link to code example sandbox jsx import react from react export default function app const enable setenable react usestate true return setenable evt target check disable the above fieldset by unchecke the checkbox check the box once again do not re enable the fieldset however the current behavior enable the use the in its change the state of the in unchecked fashion it do not fire its onchange event and its value do thus no long match the state of the component the expect behavior base on the w3c and whatwg the fieldset element spec the content of the first of a should not be disable when that fieldset be disabled one would expect that if an element do not appear disabled its event will be trigger
facebookreact
bug fix bigint in copyelementpath in react devtool
Bug
this be a continuation of an previous issue to add support for the bigint data type in react devtool original pr merge this happen when you try to copy a bigint value to clipboard via react devtool would nutboltu mind take a look backend js 1 uncaught typeerror do not know how to serialize a bigint at json stringify at c backend js 1 at object copyelementpath backend js 6 at t backend js 6 at t r emit backend js 6 at backend js 32 at t backend js 8 c backend js 1 copyelementpath backend js 6 anonymous backend js 6 r emit backend js 6 anonymous backend js 32 t backend js 8 postmessage async anonymous contentscript js 1 app insight app insight 50 uncaught typeerror can not read property message of null at trackerror app insight app insight 50 at eval app insight app insight 22 trackerror app insight app insight 50 eval app insight app insight 22 settimeout async eval app insight app insight 21 error async initappinsight app insight app insight 17 main vm70658 client 101 main node module tessin tcm lib dev boot loader 31 async function async main node module tessin tcm lib dev boot loader 27 anonymous 219 3435 backend js 1 uncaught typeerror do not know how to serialize a bigint at json stringify at c backend js 1 at object copyelementpath backend js 6 at t backend js 6 at t r emit backend js 6 at backend js 32 at t backend js 8 c backend js 1 copyelementpath backend js 6 anonymous backend js 6 r emit backend js 6 anonymous backend js 32 t backend js 8 postmessage async anonymous contentscript js 1 app insight app insight 50 uncaught typeerror can not read property message of null at trackerror app insight app insight 50 at eval app insight app insight 22 trackerror app insight app insight 50 eval app insight app insight 22 settimeout async eval app insight app insight 21 error async initappinsight app insight app insight 17 main vm70658 client 101 main node module tessin tcm lib dev boot loader 31 async function async main node module tessin tcm lib dev boot loader 27 anonymous 219 3435 backend js 1 uncaught typeerror do not know how to serialize a bigint at json stringify at c backend js 1 at object copyelementpath backend js 6 at t backend js 6 at t r emit backend js 6 at backend js 32 at t backend js 8 c backend js 1 copyelementpath backend js 6 anonymous backend js 6 r emit backend js 6 anonymous backend js 32 t backend js 8 postmessage async anonymous contentscript js 1 app insight app insight 50 uncaught typeerror can not read property message of null at trackerror app insight app insight 50 at eval app insight app insight 22
facebookreact
error could not find node with i d 2153 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 4 0 f749045a5 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159909 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159855 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160378 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 323092 at ei chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 58864 at yl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 106932 at kc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99474 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99399 at fc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96173 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
question react apollo hook fail after add react native to monorepo
Question
I be try to create a react web app and react native app with monorepo by use yarn workspace so I create web and controller and it work fine I be able to make graphql query to my apollo express server but after add react native application I see this enter image description here 1 1 1 I be 100 that I be not break any react hook rule because before add react native application it be work fine be there any way how can I solve it apollo controller import usequery from apollo react hook import gql from graphql tag export const usehelloquery usequery gql hello react component function test const datum usehelloquery return awesoe before add react native it be exactly same
facebookreact
api for display name on forwardref memo and potential future exotic component
Invalid
continuation of 14319 which be close by a bot I would hope that a maintainer take the time and reopen the original issue and close this one thank tl dr can you expose share getcomponentname do you want to request a feature or report a bug expose an api to get the display name of every component in dev only what be the current behavior most of the ecosystem still use component displayname component name somefallbackname with some branch depend on the type of component when set the display name of an enhanced component I e connect wrappedcomponent will result in connect wrappedcomponent as a displayname 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 since component create by forwardref or memo be not actual function these high order component be not able to determine a proper display name while react devtool be able to react redux create connect component react router create withrouter undefine what be the expect behavior the new exotic component should work with the exist 3rd party librarie wrt to displayname now there be a couple of solution to this issue 1 edit expose share getcomponentname 2 this be the responsibility of the ecosystem it should provide a solution and maintain it somewhat block by 12882 relate 12932 3 grant access to the functionality use in react devtool or would this only work on the fiber 4 set a name or displayname no preference here property on those exotic component don t know how to call they naive implementation e g name forwardref fn name which version of react and which browser os be affect by this issue do this work in previous version of react I guess this start with forwardref in 16 3
facebookreact
question I have a lot of very nice and smart vuejs component be there a way to use it in an react project
Question
this issue tracker be not for question as it happen support request that be create as issue be likely to be close we want to make sure you be able to find the help you seek please take a look at the follow resource code question if you have a code question relate to close this page now and close this page now dom it might be well suit for stack overflow it s a great place to browse through frequent question about use close this page now as well as ask for help with specific question this page now talk to other close this page now developer there be many online forum which be a great place for discussion about good practice and application architecture as well as the future of close this page now this page nowjs org community support html popular discussion forum proposal if you d like to discuss topic relate to the future of close this page now or would like to propose a new feature or change before send a pull request please check out the discussion and proposal repository this page nowjs rfc
facebookreact
question react lib context override app context
Question
hi I believe that this can potentially be an issue though I m not sure I be wonder about good pattern concern the react context let s get a public library for example react intl that expose a provider intlprovider let s create a library barlib that use react intl to manage translation internally and that also expose a provider now let s imagine I create a web app and use both barlib and react intl I don t expect the barlib to ever override my react intl context because I m not aware it use internally the react intl lib but the barlib can accidentally override the react intl context this kinda break the isolation of lib imo I see several solution don t use an other lib context in the barlib pretty extreme check that there be not already an intl context in the barlib if so merge the context value I m not convinced with either solution what do you guy think about it
facebookreact
bug useref can not return a persist ref object
Question
react version 16 12 0 step to reproduce 1 click button view print datum 2 click button view print datum link to code example the current behavior every time you click the button the print datum will change the expect behavior every time I click the button the print datum should be an empty object
facebookreact
doc react documentation be the documentation I have ever see it dosent even properly tell how to get start and create new app take some inspiration from documentation of django flutter vue angular etc
Invalid
this issue tracker be not for documentation issue the react website be host on a separate repository you may let the team know about any issue with the documentation by open an issue there
facebookreact
bug uncaught typeerror can not read property nextsibling of null
Bug
I be use react rehype late version to parse and format markdown content that be continuously update base on user input on certain change particularly the creation of list item I get an error message uncaught typeerror can not read property nextsibling of null before I see the error message in the console I see an unclosed comment tag when I inspect the element that be render the formatted text screenshot 2020 01 13 at 9 59 45 am the stack trace be all within react code screenshot 2020 01 13 at 9 57 33 am react version 15 6 0 step to reproduce small repo with repro step be at the current behavior eventually the component crash in react code that update the component on state change the expect behavior there be no js error crash
facebookreact
question why cann t I set echart instance use usestate
Question
code question I try to store the echart instance use usestate but after setinstance instance be always undefined const instance setinstance usestate undefined const chartinstance echart init root current setinstance prev console log prev instance prev first time undefine then echart instance return prev chartinstance console log instance instance chartinstance instance be always undefined
facebookreact
the bad arabic translation
Question
language and translation I m sure that you translate your react site by google the bad result at all I hope you correct it
facebookreact
react devtool extension bug uncaught typeerror can not read property sub of undefined when navigate to plain text page
Bug
react developer tool 4 4 0 f749045a5 1 3 2020 from chrome webstore chromium 81 0 4024 0 snapshot ubuntu 18 04 step to reproduce 1 open chrome with react developer tool instal 2 open developer console 3 in console setting cogwheel in console s top right corner check preserve log checkbox to make sure that the log be not overwrite on navigation 4 navigate to a react enable website e g 5 navigate to a plain text page such as the current behavior error be print in console backend js 32 uncaught typeerror can not read property sub of undefined at g backend js 32 at e backend js 8 g backend js 32 e backend js 8 postmessage async a contentscript js 1 117 contentscript js 1 n contentscript js 1 anonymous contentscript js 1 anonymous contentscript js 1 where backend js be a link to chrome extension fmkadmapgofadopljbjfkapdkoienihi build backend js fmkadmapgofadopljbjfkapdkoienihi be an i d of react developer tool I verify by open chrome extension and perform page search for this i d the expect behavior no error note it s a convoluted usecase but I think it may help to catch bug for more important one I be not sure whether it s plain text ness of the page that be important but that s how you can reproduce it the hypothesis be that dev tool do not expect html tree to disappear on navigation or either extension enter a state where it can not digest the plain text page and it probably shouldn t try p s thank for the refresh extension it make dev experience so wonderful
facebookreact
help when I use react createelement directly and how to pack the component
Question
hello all I be meet a problem when I publish a react component I need to help and discuss with you all I be go to write a component to load react component from cdn and make it like a wrapper component jsx import react component from react import scriptjs from scriptjs const dev script const prod script class phoenixheaderwrapper extend component constructor prop super prop this type null this scripturl prop scripturl prop env prod dev script prod script this state cmp null componentdidmount scriptjs this scripturl this type window phoenixheader this createorupdatecomponent createorupdatecomponent const scripturl otherprop this prop if this type console error load component fail return const cmp react createelement this type otherprop this be point this setstate cmp render const cmp this state return cmp phoenixheaderwrapper defaultprop scripturl env prod export default phoenixheaderwrapper and then I do it just like do a normal react component that I be set the webpack config like below js phoenixheader output publicpath filename phoenix header js path path appbuild library phoenixheader librarytarget commonjs2 libraryexport default mode production external react commonj react commonjs2 react amd react root react react dom commonj react dom commonjs2 react dom amd react dom root reactdom and then I run the npm run build npm publish to publish it in my own object which use the phoenixheader component as a npm package jsx app jsx import react from react import phoenixheader from phoenix header import app css function app return edit src app js and save to reload learn react export default app after npm start it show I a error image that it be my confusion be why createelement not in this scope so I try to make react set into global js window react react yes it s work for I but someone would like to tell I why need to make react set into global and be I need to build this wrapper component which do not external the react when I be build let s discuss or give I more suggest about this wrapper component please
facebookreact
error could not find node with i d 32 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
error could not find node with i d 350 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
error f hasownproperty be not a function
Bug
describe what you be do when the bug occur 1 open component tree 2 click context provider 3 click someprovider component right above that context provider this issue do not happen if I click someprovider first only after click context provider within this someprovider wrapper component please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at ha chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 268899 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46436 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 3676 at o chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46146 at na chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46382 component stack in ha in div in ya in ea in div in div in ya in ea in div in unknown in div in bi in div in ai in suspense in ei in div in div in la in ur in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
devtool component inspector not load for large component
Bug
do you want to request a feature or report a bug bug report what be the current behavior the component inspector work fine on most component but on one that be particularly large with many large prop it be stick on loading 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 you should be able to reproduce the issue on navigate to the component with the key jonloyen an intro to dataworld dataset other component above and below that one will load but that one specifically will not what be the expect behavior it should load the component tree eventually previous to the 4 3 0 update these component load fine which version of react and which browser os be affect by this issue do this work in previous version of react our app use react version 16 8 3 I be on dev tool version 4 3 0 on chrome 79 0 3945 88 on macos catalina 10 15 2 but other on early version of macos be have the same issue I have a suspicion that this may be relate to as this change have make a big impact on our app mostly in a good way we use immutablejs and that change have make it much easy to navigate immutable prop since it preload the value the component that be load slowly use a proportionately large number of immutable prop to other component
facebookreact
in react and react dom 16 upgrade get error uncaught typeerror can not read property input of undefined
Question
I be try to upgrade my reactjs and react dom version from v15 6 2 to v16 0 0 and be get the above error click through the error in the console I see that the react dom be undefined I have follow all the migration instruction on the react org site and look extensively but can not seem to get rid of this error on version of react and react dom of v16 and above any idea on what that issue be and how I can resolve it below be my package json and webpack config they be pre upgrade to v16 but I have try add core js per reactjs org var react dom react2 default dom input react dom input here be the highlight error select react dom select textarea react dom textarea my dependency in package json devdependencie babel loader 7 1 5 babel preset es2015 6 1 18 babel preset react 6 1 18 babel preset stage 0 6 24 1 chai 4 1 2 chai jquery 2 0 0 css loader 1 0 0 eslint config rallycode 3 2 0 mocha 5 2 0 react addon test util 15 0 1 style loader 0 21 0 webpack cli 3 1 0 webpack dev server 3 1 8 dependency actioncable 5 2 4 axio 0 18 0 babel core 6 2 1 babel polyfill 6 26 0 babel preset stage 1 6 1 18 cloudinary core 2 5 0 cloudinary react 1 0 6 dotenv webpack 1 5 5 file loader 2 0 0 jquery 3 3 1 jsdom 12 0 0 lodash 4 1 0 prop type 15 6 1 react 15 6 2 react bootstrap 0 32 1 react day picker 7 1 6 react dom 15 6 2 react dropzone 5 0 1 react helmet 5 2 0 react redux 5 0 7 react router dom 4 3 1 react stripe element 2 0 1 redux 4 0 0 redux form 7 4 2 redux thunk 2 2 0 sha1 1 1 1 webpack 4 17 2 my webpack config const webpack require webpack const dotenv require dotenv webpack const raf require raf const path require path module export mode none watch false entry babel polyfill src index js output path dirname publicpath filename bundle js module rule test jpg png svg use loader file loader option name path name hash ext test js exclude node module use loader babel loader option preset react es2015 stage 0 end of loader devserver historyapifallback true contentbase plugin new webpack defineplugin process env node env json stringify process env node env new dotenv
facebookreact
error could not find node with i d 27720 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at qi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 67999 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108660 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
error could not find node with i d 834 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
error could not find node with i d 815 in commit tree
Bug
screenshot 2020 01 07 at 5 14 39 pm describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
allow load information from my component
Duplicate
do you want to request a feature or report a bug its a bug what be the current behavior I m try to watch all the property in the tab component but it get stick when I click in a component from my project I ve try this in all my repository and I get the same problem image what be the expect behavior its suppose to show al the info from my component which version of react and which browser os be affect by this issue do this work in previous version of react react 16 7 0 browser chrome os apple s macos and this be work the last weekend with no problem
facebookreact
error could not find node with i d 1804 in commit tree
Bug
describe what you be do when the bug occur 1 open profiler 2 record session 3 click rank button please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
error context menu with i d selectedelement already register
Bug
describe what you be do when the bug occur 1 just try to use component tab edit error seem to appear use firefox not chrome please do not remove the text below this line devtool version 4 4 0 f749045a5 component stack in vo in bi in div in ai in suspense in ei in div in div in la in ur in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
render react component on server to take a screenshot of it
Question
my react application have a list of to do list like this replace the figma canvas preview image with todo list above in the list of todo list I d like to include a preview of each list as well as its name here s what I think of to achieve this whenever a todo list be update run a aws lambda node js environment job which generate html for the todo list server side use reactdomserver renderstaticmarkup then serve that html locally visit the page use puppeteer and take a screenshot of the page however this seem like a lot of work be there an easy way of achieve this be there anything in the step above that win t work I ve look at repng 1 so far but it hasn t work for the component I test it with 1
facebookreact
error could not find node with i d 1145 in commit tree on react profiler
Bug
describe what you be do when the bug occur 1 open ranked tab 2 change render at repeatedly 3 error appear please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at qi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 67999 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108660 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
can not analyse component state
Bug
do you want to request a feature or report a bug bug what be the current behavior on try to analyse a component state use react developer tool the analyse pane stay in the loading state and throw this error js uncaught typeerror can not read property name of undefined at o backend js 1 at s backend js 1 at s backend js 1 at s backend js 1 at l backend js 1 at object inspectelement backend js 6 at t backend js 6 at t r emit backend js 6 at backend js 32 at t backend js 8 what be the expect behavior able to analyse component state as in the previous react dev tool version which version of react and which browser os be affect by this issue do this work in previous version of react react developer tool version 4 3 0 12 20 2019 react version 16 4 0 browser chrome version 79 0 3945 88 official build 64 bit brave version 1 1 23 chromium 79 0 3945 88 official build 64 bit
facebookreact
react developer tool react router dom e hasownproperty be not a function can not read property name of undefined
Bug
bug uncaught typeerror can not read property name of undefined uncaught typeerror e hasownproperty be not a function infinite loading in component view image reproduce use hook userouter or hoc withrouter from react router dom and select component with hook hoc in component view react developer tool issue be cause by not bug query object do not have constructor and do not have hasownproperty image image image
facebookreact
error f hasownproperty be not a function
Bug
describe what you be do when the bug occur 1 open 2 open devtool and try to inspect the component please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at ha chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 268899 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107431 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 at vc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 96672 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46436 at n unstable runwithpriority chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 3676 at o chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46146 at na chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46382 component stack in ha in div in ka in div in bi in div in ai in suspense in ei in div in div in la in ur in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
devtool can t inspect object without prototype
Bug
do you want to request a feature or report a bug bug what be the current behavior 1 select a component 2 the right panel property panel always show loading 3 the follow error be print to the console backend js 1 uncaught typeerror can not read property name of undefined at o backend js 1 at s backend js 1 at s backend js 1 at l backend js 1 at object inspectelement backend js 6 at t backend js 6 at t r emit backend js 6 at backend js 32 at t backend js 8 image I don t know why you minify the output but the call stack point to here l391 if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior react devtool display the prop of the select component which version of react and which browser os be affect by this issue do this work in previous version of react react 16 12 0 chrome 79 0 3945 88 idk
facebookreact
error could not find node with i d 2456 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 3 0 3e0967783 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159833 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 159779 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 160302 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 322998 at ii chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59363 at qi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 67999 at sl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108660 at ic chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99973 at tc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 99898 component stack in sl in div in div in div in vo in unknown in n in unknown in div in div in qi in ve in nn in da in yc
facebookreact
my navbar work fine until next day
Question
hi I m newbie for web dev I m start learn react and next js and I get issue now I have to do a navbar so I use navbar from reactstrap to my next js project it work fine but nextday I open my project and then my project kaboom error invalid hook call hook can only be call inside of the body of a function component this could happen for one of the follow reason 1 you might have mismatch version of react and the renderer such as react dom 2 you might be break the rule of hook 3 you might have more than one copy of react in the same app see for tip about how to debug and fix this problem 2 stack frame be collapse example component mainnav js 19 16 import bootstrap dist css bootstrap min css 17 18 const example prop 19 const isopen setisopen usestate false 20 21 const toggle setisopen isopen 22 view compile 11 stack frame be collapse this be my navbar code import react usestate from react import collapse navbar navbartoggler navbarbrand nav navitem navlink uncontrolleddropdown dropdowntoggle dropdownmenu dropdownitem navbartext from reactstrap import bootstrap dist css bootstrap min css const example prop const isopen setisopen usestate false const toggle setisopen isopen return reactstrap home what who branch where when faqs game simple text export default example what wrong be it and what should I do to resolve this thank
facebookreact
error could not find commit datum for root 5621 and commit 7
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at n value chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 163226 at m chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332702 at uc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 332919 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at el chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 68139 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 108547 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 46341 component stack in uc in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
error could not find node with i d 57 in commit tree
Bug
I m try to use profilter tool on chrome browser but I get this error when I review the rank of list element I don t know what be that devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
I can t get the late status value in the initialization method
Question
I try to get the late state value in the initialization method but the result be not satisfactory all this happen in function component 1 react version be 16 12 0 2 react dom version be 16 12 0 this be my demo code import react usestate useeffect from react const app button click const btnclick console log initbutton get state be nowstate can t get now state all be init value init a button const inittitle return click const title settitle usestate now state const nowstate setnowstate usestate 0 console log now state be nowstate useeffect settitle inittitle return title setnowstate nowstate 1 change now state export default app
facebookreact
hydrate svg error expect server html to contain a matching in
Bug
do you want to request a feature or report a bug bug what be the current behavior it seem like reactdom hydrate doesn t play nice with certain kind of inline svgs specifically one that have clippath s when nextjs try call hydrate on a page with one of these svg the offend part of the svg flash quickly then react throw this error to the console expect server html to contain a matching in I have a very small example of this happen here the strange part be when next build the site statically it all work I originally open this issue on zeit nextjs but timneutken suggest I open the issue here see for all the detail what be the expect behavior the svg contain the clippath get render correctly on the client side which version of react and which browser os be affect by this issue do this work in previous version of react react 16 12 not sure about previous version browser firefox and chrome os macos
facebookreact
more clear hook warn for why a function be not consider as a component
Good First Issue
do you want to request a feature or report a bug bug what be the current behavior in current behaviour I can create a functional component that start with lowercase and I can use it by import it with the uppercase name but if I start use hook in this lowercase name component react will give error react hook usestate be call in function login which be neither a react function component or a custom react hook function react hook rule of hook 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 reproduce bug here what be the expect behavior the expect behaviour be that I should get a warning at the first point when I be create a component which start with lowercase and if I be use hook into a functional component that start with lowercase then it should give useful warning something like start component with uppercase I know as a developer that I should always start my component with uppercase letter but if by mistake someone create a component with a lowercase letter and try to use hook he will have no clue what be wrong with his code which version of react and which browser os be affect by this issue do this work in previous version of react react 16 12 0 react dom 16 12 0 react script 3 3 0 chrome 79 0 3945 88 official build 64 bit os ubuntu 18 04 3 lts x86 64
facebookreact
error could not find node with i d 5268 in commit tree
Bug
describe what you be do when the bug occur 1 click rank in profiler 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
error could not find node with i d 318 in commit tree
Bug
describe what you be do when the bug occur 1 start stop profile 2 click rank tab please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
function pass as parameter and save in context api store take old store from context api
Question
when I get 401 status code from backend I run refreshtoken method with pass the function where expire token occur in refreshtoken method I get new token and set in refreshtokenlastfunc property function from parameter then I watch when refreshtokenlastfunc be update use react useeffect and run once again the function where expire token occur the problem be while I run store refreshtokenlastfunc in useeffect the function in refreshtokenlastfunc property use old context api store so it use old token not the new one you can read my comment in useeffect for store refreshtokenlastfunc do you want to request a feature or report a bug I don t actually know if it be a react bug or I don t understand js properly what be the current behavior if I run store refreshtokenlastfunc function in useeffect it take old store not the new one what be the expect behavior I want store refreshtokenlastfunc function to run with new store because store be modify before this function run which version of react and which browser os be affect by this issue do this work in previous version of react react verison 16 12 0 browser google chrome 79 my code js export const storeprovider prop const gettoken localstorage getitem token const initstate token gettoken isauth false userrole old role mainurl mainurl apiurl apiurl refreshtokenlastfunc const store setstore usestate initstate const getuserinfo async if gettoken try const apiconfig method get header content type application json authorization bearer store token const response await fetch store apiurl get I apiconfig const responsejson await response json if response ok update context api setstore store userrole responsejson role username responsejson name usergroupid responsejson group i d isauth true else if response status 401 refreshtoken getuserinfo else throw new error some error occur catch error console log error const refreshtoken async func try const apiconfig method get header accept application json authorization bearer store token const response await fetch store mainurl refresh token apiconfig const responsejson await response json if response ok update token in local storage localstorage setitem token responsejson token update context api setstore store userrole new role token responsejson token refreshtokenlastfunc func else throw new error some error catch error throw error useeffect getuserinfo useeffect if I console log my store before call function store be correctly update but the function use old store console log store from useeffect store store userrole new role which be correct store refreshtokenlastfunc store userrole old role which should be new role store refreshtokenlastfunc return prop child
facebookreact
typescript be there any way to define the state variable when use functional component
Question
if there be a lot of state variable I guess it be hard to get a whole picture the state variable verse class component do you want to request a feature or report a bug what be the current behavior if the current behavior be a bug please provide the step to reproduce and if possible a minimal demo of the problem your bug will get fix much fast if we can run your code and it doesn t have dependency other than react paste the link to your jsfiddle or codesandbox example below what be the expect behavior which version of react and which browser os be affect by this issue do this work in previous version of react
facebookreact
error could not find node with i d 6 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
error could not find node with i d 72 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
how can I change react umd version in node module
Question
I see react package have cjs and umd folder and index js in react output cjs version so if I want to use umd how can I change image
facebookreact
getderivedstatefromprop be execute after setstate 13015
Question
ideally getderivedstatefromprop should not be call due to current component s setstate but it be behave so can someone explain couldn t find solution in 13015
facebookreact
error could not find node with i d 66 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc
facebookreact
opinion on ionic reac
Question
hello feasibility of make a project in ionic reaction I be interested in know more about ionic react and I would like to know if it be advisable to do a project with ionic react how scalable the project would be and you can use all the tool that have both ionic and rea example camera map notification route among other I appreciate if you can advise I thank you
facebookreact
error could not find node with i d 50 in commit tree
Bug
describe what you be do when the bug occur 1 2 3 please do not remove the text below this line devtool version 4 2 1 3816ae7c3 call stack at chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157108 at map foreach at commitindex chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157054 at e getrankedchartdata chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 157577 at vl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 40 314907 at gi chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 59907 at jl chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 107381 at lc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92715 at pc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 92640 at wc chrome extension fmkadmapgofadopljbjfkapdkoienihi build main js 32 89544 component stack in vl in div in div in div in will in unknown in n in unknown in div in div in li in e in dn in ca in pc