Load es5 polyfills on ng test

[filipesilva]

🐞 Bug report

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: CLI 7

Description

The new polyfills-es5.js chunk is generated for ng test but never loaded.

🔬 Minimal Reproduction

The browser builder loads es5 polyfills by injecting them into the index html in

angular-cli/packages/angular_devkit/build_angular/src/angular-cli-files/models/webpack-configs/browser.ts

Line 48 in 8089a3f

noModuleEntrypoints: ['polyfills-es5'],

The karma builder has a two special index.html that it loads, and only the normal polyfills are listed

• angular-cli/packages/angular_devkit/build_angular/src/angular-cli-files/plugins/karma-context.html

  Line 31 in 8089a3f

  <script src="_karma_webpack_/polyfills.js" crossorigin="anonymous"></script>

• angular-cli/packages/angular_devkit/build_angular/src/angular-cli-files/plugins/karma-debug.html

  Line 32 in 8089a3f

  <script src="_karma_webpack_/polyfills.js" crossorigin="anonymous"></script>

It should also be added to the list in

angular-cli/packages/angular_devkit/build_angular/src/angular-cli-files/plugins/karma.ts

Line 211 in 8089a3f

'/_karma_webpack_/polyfills.js',

@clydin also mentioned that the karma loaded scripts (

angular-cli/packages/angular_devkit/build_angular/src/angular-cli-files/plugins/karma-context.html

Lines 38 to 40 in 8089a3f

	<script type="text/javascript">
	window.__karma__.loaded();
	</script>

) might be problematic in conjunction with module scripts because they defer by default, and recommend having a module and nomodule version of the karma script.

🔥 Exception or Error

Unsure, probably missing native stuff on older browsers.

🌍 Your Environment

@angular/[email protected]

Anything else relevant?

[angular-automatic-lock-bot]

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.}