|
|
|
* define api for production and dev inside services/api.config.ts at the top
|
|
|
|
### Why Webpack?
|
|
|
|
We are choosing to use webpack as our development environment for a variety of reasons:
|
|
|
|
* powerful loader/transpiler pipelines
|
|
|
|
* has a robust development server
|
|
|
|
* avoids the ridiculous SystemJS config that the Angular team shows in their docs
|
|
|
|
* ability to break out entire components into webpack bundlable chunks, which could potentially be loaded independently over HTTP/2
|
|
|
|
* hot module replacement (right now mainly for style, eventually for entire dom components)
|
|
|
|
|
|
|
|
|
|
|
|
notes
|
|
|
|
* import new dependencies into the vendors.ts file
|
|
|
|
config, vendors, polyfills
|
|
|
|
* (webpack because: HMR, chunk (component) bundles, avoid silly SYstem config in angular docs) |
|
|
\ No newline at end of file |
|
|
|
* config, vendors, polyfills |
|
|
\ No newline at end of file |
