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
Does --extractErrors fully work? It does update the file, but I'm still seeing "out of sync" console spam on rebuilds.
What happens if user forgets to envify process.env.NODE_ENV with webpack or use dead code elimination? Would it bundle both bundles? Sounds like even worse than what happens now. Would the user see any warnings?
The bundle size analysis could be done in a Dangerfile. Jest uses the build job for a variety of arbitrary tasks like scanning for "use strict", for example.
I think we've done everything planned here. GCC advanced is still not there but we have a separate issue tracking it. No plans to share build process with other renderers for now.
Now that flat bundles are mostly done (#9327), separating out followup work into a separate issue.
ReactDebugCurrentFrame
be in isomorphic package? Make ReactDebugCurrentFrame shared state between core and renderers #9365--extractErrors
fully work? It does update the file, but I'm still seeing "out of sync" console spam on rebuilds.process.env.NODE_ENV
with webpack or use dead code elimination? Would it bundle both bundles? Sounds like even worse than what happens now. Would the user see any warnings?invariant
issue (I think they wanted it to be ignored so it's used verbatim)providesModule
in sourceobject-assign
on React internals) Share Object.assign polyfill between UMD builds #10671Extract shared state to npm packageThe text was updated successfully, but these errors were encountered: