Skip to content

Component ID generation collision detected is thrown after first change when running default angular installation #25924

Closed
@eneajaho

Description

@eneajaho

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

Component ID generation collision detected is thrown after first change when running default angular installation

Minimal Reproduction

  1. npm create @angular@next
  2. Choose ssr to be enabled
  3. ng serve
  4. change app component html -> no warning
  5. change app component html again -> warning is shown in console

CleanShot 2023-09-29 at 11 56 57@2x

Exception or Error

No response

Your Environment

Angular CLI: 17.0.0-next.6
Node: 18.17.0
Package Manager: npm 9.6.7
OS: darwin arm64

Angular: 17.0.0-next.6
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.0-next.6
@angular-devkit/build-angular   17.0.0-next.6
@angular-devkit/core            17.0.0-next.6
@angular-devkit/schematics      17.0.0-next.6
@schematics/angular             17.0.0-next.6
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.0

Anything else relevant?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions