Skip to content

Changes will no longer be recognized if you remove and re-add same component #28956

Open
@dariosko

Description

@dariosko

Command

serve

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Changes will no longer be recognized if you remove and re-add same component.

Minimal Reproduction

Removing and re-adding the import of the component (import { TestComponent } from ‘./test/test.component’), the component in the imports array and in the template (<app-test>) leads to that no further changes to this component are recognized.

Image

Repro App V18

Problem also in V19

Exception or Error


Your Environment

**v18 Reproduction environment:**
Angular CLI: 18.2.12
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 18.2.12
... animations, build, cli, common, compiler, compiler-cli, core
... forms, platform-browser, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1802.12
@angular-devkit/core         18.2.12 (cli-only)
@angular-devkit/schematics   18.2.12
@schematics/angular          18.2.12
rxjs                         7.8.1
typescript                   5.5.4
zone.js                      0.14.10

**v19 Reproduction environment:**
Angular CLI: 19.0.0
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.0.0
... animations, build, cli, common, compiler, compiler-cli, core
... forms, platform-browser, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1900.0
@angular-devkit/core         19.0.0
@angular-devkit/schematics   19.0.0
@schematics/angular          19.0.0
rxjs                         7.8.1
typescript                   5.6.3
zone.js                      0.15.0

Anything else relevant?

After clearing the Angular cache with ng cache clean and restarting the dev server with ng serve it works again.
So probably a caching bug.

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions