This adds the new parameter `missingTranslation` for AoT that was added in angular/angular/pull/15987 and that lets you define the MissingTranslationStrategy
Adds sourcemap and minification to javascript added via the `scripts` array in `.angular-cli.json`.
`script-loader` is no longer used, which should help with CSP since it used `eval`.
Scripts will no longer appear in the console output for `ng build`, as they are now assets instead of webpack entry points.
It's no longer possible to have the `output` property of both a `scripts` and a `styles` entry pointing to the same file. This wasn't officially supported or listed in the docs, but used to be possible.
Fix#2796Fix#7226Fix#7290
Related to #6872
The type of entryFiles from entryPoint is array in webpack official suggested, but actually it could be string. The error caused by `every` method which is only invoked by array, however entryFiles is a string. Solution: if entryFiles is not array, make it as an array which includes just a single string element.
If an ng app was created with an older version of ng CLI, while the global
ng CLI is more recent, one cannot perform ng completion INSIDE that app folder.
This is due to the warning being written to stdout, which if appended to
~/.bashrc causes the shell to fail to process the English text as commands.
The solution is to display the warning to stderr without producing the
completion output.
In good Unix style, a non-zero status code must returned.
This PR fixes#6343.
The PR introduces a breaking change:
- the warning is written to stderr -
- no output is produced
- different status code returned
When calling ng help -s / --short one gets a shorter output; basically only ng + command, followed by the command's description.
No breaking change, as it introduces a new flag.
karma plugin relies on source-map-support being a dependency of karma-source-map-support and npm 3+ flat dependency tree.
https://github.com/pnpm/pnpm/issues/863
Webpack is updating to `enhanced-resolve@3.4.0` (16bf0b6f26) but the CLI cannot do so yet (see #7123).
This PR pins `webpack@3.3.0` until we are able to update to `enhanced-resolve@^3.4.0`.
