javascript - AngularJS modules vs CommonJS/ECMA6 modules -
i've joined ongoing web project frontend written in angular 1 mvc framework , using webpack build system , i'm feeling neo in matrix 2 in stack of nested matrices. the project split separate .js files, each annotated module in either commonjs style (with require , module.exports ) or ecma6 style (with import s , export s). webpack transpiles ecma6 ecma5 babel , creates single bundle them. within commonjs modules reside angularjs modules. living inside commonjs, angular task of dependency injection of own angular's requirejs-esque module system. i'm feeling same job of dependency management done twice. is true, when angular written, angular developers had in mind multi-module angular projects should've been concatenated e.g. grunt concat single bundle , served client, angular $injector responsible dependency management? so, our webpack build over-complication on top of that? example project: file model.module.js : import angular "angular...