You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rats. Looks like an oversight in the way the schedule/tracking endpoint doesn't initialize its refs in production mode. I hadn't really been considering the use of profiling react-dom with non-profiling schedule/tracking 😦
Fastest fix would be to put out a bugfix release of schedule/tracking production bundle that initializes the refs. Shouldn't impact non-profiling react-dom since its production bundle doesn't even require schedule/tracking
Not sure if we'd want to warn about this from react-dom profiling bundle, since we don't normally do warnings in production bundles.
I can't quite figure out how to use the profiling build. I aliased
react-dom
toreact-dom/profiling
but I get this error:I didn't want interactions, I just want profiling. What am I doing wrong?
To repro, use CRA, then eject, then add
react-dom
->react-dom/profiling
to alias in webpack prod config and build.The text was updated successfully, but these errors were encountered: