GeezerVison

PR Checklist

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

When the workspace sets "@schematics/angular:component": { "type": "component" }, ng generate application --file-name-style-guide=2025 inherits that type for its root component. It generates app.component.css, while the application template generates app.ts referencing ./app.css. The first build fails with NG2008, and extra app.component.* files are left in the application.

Issue Number: Closes #34684

What is the new behavior?

Pass an explicit empty type when generating the application root component with the 2025 naming style, so the component files match the application templates: app.ts, app.html, and app.css.

The 2016 branch continues to pass type: 'component'. Ordinary component generation still uses the workspace default. This follows the approach used in #34450 and #34472.

The new E2E test sets the workspace component type, generates and builds applications using both naming styles, checks their stylesheet references and the absence of the incorrectly named root component, and verifies that a separately generated component still uses the workspace type.

Does this PR introduce a breaking change?

• Yes
• No

Other information

Validated locally against main at d5035923f0e357b2526c98110125eee04b05192f:

• Before the fix, the new regression test fails during the generated application's build with NG2008.
• After the fix, the regression test and the existing schematic-defaults E2E test both pass.
• The Angular schematics unit suite reports 976 specs, 0 failures, and 1 existing pending spec.
• Prettier, ESLint on the production file, and git diff --check pass.

Commands:

pnpm bazel test //tests:e2e_node24 \
  --config=e2e --config=no-sharding \
  --test_filter='tests/generate/{application/application-workspace-type-default,schematic-defaults}.ts' \
  --test_arg=--esbuild --nocache_test_results

pnpm bazel test //packages/schematics/angular:test --config=no-sharding

The full CLI repository test suite was not run.