ng new logs a warning about entryComponents being deprecated

[cexbrayat]

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• 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: v10.0.x

Description

When running ng new, a warning about entryComponents is logged

🔬 Minimal Reproduction

🔥 Exception or Error

> ng new entry-comp-warning --defaults
Option "entryComponent" is deprecated: Since version 9.0.0 with Ivy, entryComponents is no longer necessary.
CREATE entry-comp-warning/README.md (1034 bytes)
CREATE entry-comp-warning/.editorconfig (274 bytes)
CREATE entry-comp-warning/.gitignore (631 bytes)
CREATE entry-comp-warning/angular.json (3662 bytes)
CREATE entry-comp-warning/package.json (1261 bytes)
...

🌍 Your Environment

Angular CLI: 10.1.0
Node: 14.6.0
OS: darwin x64

Angular:
...
Ivy Workspace:

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1001.0
@angular-devkit/core         10.1.0
@angular-devkit/schematics   10.1.0
@schematics/angular          10.1.0
@schematics/update           0.1001.0
rxjs                         6.6.2

Anything else relevant?

npx @angular/cli@10.0.8 new entry-comp-warning --defaults does not raise this warning.

[alan-agius4]

Ummm, this is an interesting one!

[prabh-62]

> npx @angular/cli@11.0.0-next.6 new admin-console --strict true --routing true --style css
outputs zero warnings

> npx @angular/cli@11.0.0-next.6 new admin-console --strict true --defaults true
spawns few warnings

Option "lintFix" is deprecated: Use "ng lint --fix" directly instead.
Option "entryComponent" is deprecated: Since version 9.0.0 with Ivy, entryComponents is no longer necessary.
Option "lintFix" is deprecated: Use "ng lint --fix" directly instead.