Replace custom module loading with a webpack build step
While implementing the vue server-side-rendering spike, we had issues with JS
tooling such as webpack because the module alias system isn't understood. It
also breaks IDE navigation and refactoring and violates the principle of least
surprise. That's little benefit over typing out relative paths (or having the
IDE do it for you).
This comes with the downside of a build step, but we need that anyway to adopt
current JS language features without losing browser compatibility. It will also
allow us to enable modern developer tooling like hot reloading.
For now we would probably need to commit the result of the build to the
repository, although I'd prefer the build to be run on Jenkins and the result
stored in a artifact repository instead since this will create big diffs and is
Some things to do:
- add babel for ES2015+ support
- production build config
- webpack-dev-server / hot module reloading