Builder

[Reinmar]

Based on the current state of things I've posted the https://github.com/ckeditor/ckeditor5-design/wiki/Building article. It explains how we understand building (that it's not bundling), common scenarios and how it relates to module paths.

This model currently works for us very well. The previous one was based on AMD modules and tuning up Require.JS so its able load files from multiple weird paths. That model was insufficient as:

• it required hacking Require.js,
• it made it unclear how we could build for Node.js,
• it wasn't clear at what point we can transpile the code. So far we've been using only ES6 features supported by Chrome, but at some point we would also need to test the code against other browsers.

The implementation of the builder helped us in cleaning up this situation and opened new possibilities.

• The build for Node.js is super clean and requires no hacks.
• Build for AMD is clean as well, although we're not yet entirely sure about bundling.
• We're able to build ES6 modules which will work fine once they are implemented by browsers (I tested them with System.JS loader).
• We can add more Babel plugins at any point. For the development purposes we use only transpiler for ES6 modules, what keeps the code readable without source maps, but we are able to load more to run tests on other browsers.

[Reinmar]

We dropped the idea of a custom compilation steps which was gathering files from all the packages into simple "build". We based on ES6 modules and normal, Node.js compatible way of resolving paths (which is supported by Webpack, Browserify and Rollup with plugins).