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
@gaearon I normally bundle React and all its add-ons in a different file from my application, but when using ReactPerf I forgot of including it in the same bundle of React and ReactDOM, so I noticed I was receiving an empty array from ReactPerf functions every time I was using them, and that is because ReactDebugTool is different for the application and for React which means flushHistory is also different.
What do you think about warning the user if there are more than one instance of ReactPerf/ReactDebugTool in the page?
The text was updated successfully, but these errors were encountered:
This seems like the same issue as "duplicate React".
Can you share more into about how your setup ended up including two Reacts? It is not immediately obvious. Did you use UMD bundle and a CommonJS module?
I’m not sure what’s wrong there but I suspect it’s related to the “vendor” configuration in Webpack config. I’m not a Webpack expert so I’m not sure how we can help here, but it’s not an issue on React side so I’ll close. We will be changing how we package things anyway as part of #6351, and there is also #6812 which is very related to this issue, so let’s continue discussion there.
@gaearon I normally bundle React and all its add-ons in a different file from my application, but when using ReactPerf I forgot of including it in the same bundle of React and ReactDOM, so I noticed I was receiving an empty array from ReactPerf functions every time I was using them, and that is because ReactDebugTool is different for the application and for React which means flushHistory is also different.
What do you think about warning the user if there are more than one instance of ReactPerf/ReactDebugTool in the page?
The text was updated successfully, but these errors were encountered: