core-js dependency not removed after updating to v8

[markgoho]

🐞 Bug report

Command (mark with an x)

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

Is this a regression?

No.

Description

Per #13954 (comment) - should the project dependency on core-js be removed when updating? It isn't present in new v8 projects.

🔬 Minimal Reproduction

Run ng update @angular/cli @angular/core on a v7 project. See that after the update, core-js is still listed as a dependency.

[destus90]

I've upgraded my project some days ago and these polyfills were deleted from my polyfills.ts file.

import 'core-js/es6/symbol';
import 'core-js/es6/object';
import 'core-js/es6/function';
import 'core-js/es6/parse-int';
import 'core-js/es6/parse-float';
import 'core-js/es6/number';
import 'core-js/es6/math';
import 'core-js/es6/string';
import 'core-js/es6/date';
import 'core-js/es6/array';
import 'core-js/es6/regexp';
import 'core-js/es6/map';
import 'core-js/es6/set';

[clydin]

Removing it requires an analysis of all application code to ensure it is not used as well as any dependencies which might have a peer dependency on the package. While possible it is also complex and potentially time-intensive for large projects.

[alan-agius4]

Closing as per above comment.

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