We should use a module-loader such as webpack in kanban.
The main goal is to be able to split big angular apps such as kanban and planning-v2 in smaller components (think card-fields code). Using a module-loader, we can leverage ES 2015 modules (import, export) to use files for two or more apps, without the development overhead that we are currently experiencing for the angular artifact modal.

End goals:

• Define explicitly dependencies between files with ES 2015 modules (export, import)
• Phase out Grunt in favor of Gulp. Building the frontend should be code instead of configuration.
• Get rid of the pile of globs in build.config.js (*-service.js and co.) that we needed to build angular apps.
• Prepare for future libs (for example Angular 2+) that all leverage ES 2015 modules
• Make it easier to use future javascript standards such as ES 2015 or even Typescript
• Phase out Bower which is deprecated. Right now, we still need it for angular-ui-bootstrap-bower because there is no npm package and cloning from github gives only the source. We also need it as long as all apps using the angular artifact modal are not using module loaders.
• Ability to not "send everything" to every client. For example we could decide not to send the edit-modal related code to someone who is not admin and who cannot see it anyway.