An isolated development space with integrated fuzz testing for your components. See them individually, explore them in different states and quickly and confidently develop them.
This PR adds implicit (!) CommonsChunkPlugin support and an example with the plugin enabled.
That means we auto-detect if users use it and adapt to it by including the common chunk into our HTML files. No config needed™!
:tada:
Note: We check if users have it included by checking the constructor name in the plugins array. This means if people do something weird like import CommonsChunkPlugin as SomethingElse and then do new SomethingElse() in their plugins array, it won't work, but honestly we should discourage that anyway.
Two small points-of-action we should do after this is merged:
We should find a better (i.e. more scalable) way to pipe specific data from the core options to the plugins (like right now the dest option and the commonsChunkFilename), but that's for another PR.
We should fix the iFrame HTML having <script>undefined</script> in them, which is an artifact from my quickly-finish-this-before-react-europe coding.
nikgraf
commented
8 years ago
This PR adds implicit (!)
CommonsChunkPluginsupport and an example with the plugin enabled.That means we auto-detect if users use it and adapt to it by including the common chunk into our HTML files. No config needed™!
:tada:
Note: We check if users have it included by checking the constructor name in the plugins array. This means if people do something weird like
import CommonsChunkPlugin as SomethingElseand then donew SomethingElse()in their plugins array, it won't work, but honestly we should discourage that anyway.Two small points-of-action we should do after this is merged:
destoption and thecommonsChunkFilename), but that's for another PR.<script>undefined</script>in them, which is an artifact from my quickly-finish-this-before-react-europe coding.