Separate functionality

[kitsonk]

Enhancement

We have an opinionated build process, which is great. The challenge though comes in when someone wants or needs to reconstruct that build process as part of a larger tool chain. While we are using standard tooling, we do have some bespoke plugins that are only part of this package and we also orchestrate/configure some other plugins to meet our specific opinionated use case. So there are a couple thing we need to do in my opinion:

• Fully document the process, providing information on what is customised
• Separate out the specific plugins into separate package(s) so that someone using bare Webpack would be able to create a build pipeline without having to extract that from this CLI command (like we have with the TypeScript UMD loader).

[kitsonk]

@matt-gadd could you delineate in this issue what other functionality we need to break out into separate packages?

[kitsonk]

I have converted this to an epic and will add the other issues to it.