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

未關閉
#34,684 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@nagahara-naoki 已經在處理了。

開始於 2026年11月11日。

  • #34685 來自 @nagahara-naoki —— 未關閉

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
25/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
停滯
技術堆疊
angular, typescript
領域
build-system, cli

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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!

主要語言
TypeScript
星號
27k
分支
11.8k
平均合併
1 天 3 小時
30 天內合併 PR
271

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。