`ng generate application` produces a missing stylesheet when a workspace component type is configured

Open
  • Is something wrong?
#34,684 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@nagahara-naoki is already working on this.

Since Nov 11, 2026.

  • #34685 by @nagahara-naoki — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
angular, typescript
Domain
build-system, cli

Research direction

Start with the application schematic and its root component templates, especially the handling of component type for the 2016 and 2025 naming styles. Reproduce with the workspace-level component default and the commands in the issue, then run the application schematic’s E2E test for this case. Done means generated root component files and stylesheet references match the 2025 names and the build succeeds; the workspace default still applies to separately generated components.

Written by the indexing model from the issue text.

Description

area: @schematics/angular

Hi Angular team!

I found a case where a newly generated application fails to build when the workspace has a default component type configured.

Command

generate, build

Description

With "@schematics/angular:component": { "type": "component" } in the workspace-level schematics section of angular.json, generating an application with the 2025 file naming style produces app.component.css, but the generated app.ts references ./app.css.

As a result, the application fails its first build with NG2008. Both app.ts and an extra app.component.ts are generated.

Minimal Reproduction

  1. Create a workspace:

    ng new component-type-repro --create-application=false --defaults --package-manager=npm --skip-git
cd component-type-repro

  2. Add the following at the top level of angular.json (alongside projects):

    "schematics": {
  "@schematics/angular:component": {
    "type": "component"
  }
}

  3. Generate and build an application:

    ng generate application demo --file-name-style-guide=2025 --style=css --ssr=false --skip-install
ng build demo --configuration=development

Actual behavior

The generated files include:

projects/demo/src/app/app.ts
projects/demo/src/app/app.component.ts
projects/demo/src/app/app.component.css

There is no app.css, but app.ts contains:

styleUrl: './app.css',

Expected behavior

The root component files and their references should consistently follow the selected application naming style: app.ts, app.html, and app.css for 2025. The generated application should build successfully.

The workspace component default should still apply when generating ordinary components separately.

Exception or Error
✘ [ERROR] NG2008: Could not find stylesheet file './app.css'. [plugin angular-compiler]

    projects/demo/src/app/app.ts:7:12:
      7 │   styleUrl: './app.css',
        ╵             ~~~~~~~~~~~
Your Environment

Reproduced with the locally built CLI from main at d5035923f0e357b2526c98110125eee04b05192f, using the repository's Bazel E2E runner. Its ng version output reports:

Angular CLI       : 22.3.0-next.5
Angular           : 22.3.0-next.4
Node.js           : 24.15.0
Package Manager   : npm 12.0.2
Operating System  : darwin x64

I have not established the last working version.

Anything else relevant?
  • #31053 introduced the file naming style option and describes the 2025 root component filename as app.ts.
  • #34450 and #34472 addressed similar inheritance of the workspace component type in the app-shell and routed-module schematics. This report concerns the application schematic.

The application schematic explicitly sets the component type for the 2016 style, but leaves it unspecified for 2025. It appears that the workspace default is inherited during component generation while the application templates continue to use the 2025 filenames.

I have a local fix and an E2E regression test for this case and will follow up with a PR. Thanks for taking a look!

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
1d 3h
Merged PRs (30d)
271

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.