Description
Webpacks supports 3 different kinds of exports for its config:
- a config object, which is what Encore generates
- an array of config objects, which will then be similar to running webpack multiple times (once per config) but in a single run. This is handy when you want to isolate different shared entries entirely for instance.
- a promise resolving to one of the previous format (handy to allow building the config asynchronously if you need to load it from elsewhere)
Encore does not need to do anything special to support promises. People needing this could simply use Encore inside their promise.
However, Encore currently cannot be used for the array case (at least not without accessing internal APIs). This is because the public API of Encore is currently built around a stateful singleton.
Note that all internal APIs are ready for that though, as they rely on a non-singleton WebpackConfig object.