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
experimentalCodeSplitting introduces a relatively coherent mechanism for specifying multiple entry points and output bundle mapping, via input in array-form and object-form.
It seems like expanding those mechanisms to work beyond experimentalCodeSplitting would be the logical next step.
...or what?
The text was updated successfully, but these errors were encountered:
Non-experimentalising this is currently a top-priority. At the moment, especially @guybedford is working on updating the plugin hooks and some internal code paths. It should be finished soon, ideally with a 1.0.0 release :)
#2208 is the most important task here at the moment.
The current 0.60 release is moving towards enabling --experimentalCodeSplitting by default by enabling the flag for single-file builds as well. Further feedback very welcome before this gets unflagged.
experimentalCodeSplitting
introduces a relatively coherent mechanism for specifying multiple entry points and output bundle mapping, viainput
in array-form and object-form.It seems like expanding those mechanisms to work beyond
experimentalCodeSplitting
would be the logical next step....or what?
The text was updated successfully, but these errors were encountered: