Charles

Can you please provide the full output of the `ng version` command, including the OS and Node.js version, from both the local environment and CI environment, if possible?

@mikerentmeister If you are encountering an issue with `ngcc`, please open a separate issue with a reproduction if possible.

@Lonli-Lokli The `styles` option supports package resolution. Since the `normalize.css` package contains a main field pointing to the stylesheet, you can replace `"./node_modules/normalize.css/normalize.css"` with just `"normalize.css"`. This package resolution does...

@michaelfaith If referenced directly in the `styles` option, then they would not be supported currently. But if imported in the `styles.css` (or `styles.scss`, etc.) file generated by a new project,...

The Angular CLI will honor the configuration found in .npmrc files. If you are encountering issues in this regard please open a separate issue detailing the problem. This issue pertains...

`ng new` is intended to be a global command. The problem here is that it is also a local command (albeit a non-functional local command if within a workspace).

This adds a large amount of complexity and for the listed use cases would require building multiple apps to support all desired locales/etc. Whereas it would most likely be preferred...

Also AOT + I18n using the CLI is not really a complete solution at this point.

My point on multiple apps was mainly geared towards the quantity of output builds via the use of the environment concept in this way. (i.e., x locales * y browsers...

@hansl, what i meant was that a developer shouldn't have to run `ng build` for each translation. Angular's AOT mode requires individual builds but the CLI could manage this for...