Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task
eneajaho opened this issue Sep 29, 2023 · 1 comment · Fixed by #25927

Comments

@eneajaho
Copy link
Contributor

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

@alan-agius4 alan-agius4 self-assigned this Sep 29, 2023
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Sep 29, 2023
…uring rendering SSR

This commit clean ups the compiled components state when the build is being executed in watch mode. This is required as otherwise during development `Component ID generation collision detected` are displayed on the server.

Closes: angular#25924
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Sep 29, 2023
…uring rendering SSR

This commit clean ups the compiled components state when the build is being executed in watch mode. This is required as otherwise during development `Component ID generation collision detected` are displayed on the server.

Closes: angular#25924
alan-agius4 added a commit that referenced this issue Sep 29, 2023
…uring rendering SSR

This commit clean ups the compiled components state when the build is being executed in watch mode. This is required as otherwise during development `Component ID generation collision detected` are displayed on the server.

Closes: #25924
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.