Concatenate all source files about angular-cli HOT 5 CLOSED

Would this take into account development versus production environments? I'm a fan of the grunt-usemin, rails, or sails methods of doing this.

/* build dist/app.js */
file1.js
file2.js
file3.js
file4.js
/* endbuild */

Development would load all of this and prevent the need for source maps. Production then could add another step to concat, minify, and sourcemap.

from angular-cli.

File concatenation is an HTTP/2 anti-pattern, see https://docs.google.com/presentation/d/1r7QXGYOLCh4fcUq0jDdDwKJWNqWK1o4xMtYpKZCJYjM/edit. Angular 2 being future-oriented by nature, we should lean towards first class H2 support (which already has 70% browser support), namely no more file concatenation but rather building a depCache. Additionally production file names should be versioned with the file content hashes in order to allow long-life cache headers.

from angular-cli.

The vendor part of this issue seems to have been addressed via #163

from angular-cli.

Closing this. We will address this in the production environment build. Having different files for development is expected and makes the whole development process faster.

Please note that without a production build, the CLI is only useful for local development right now.

from angular-cli.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

from angular-cli.