Skip to content
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

component-tree.ts:352 Angular DevTools: Could not serialize injector. #56298

Closed
1 of 2 tasks
test-mhrana opened this issue Jun 6, 2024 · 2 comments
Closed
1 of 2 tasks

Comments

@test-mhrana
Copy link

Is this a bug report or a feature request?

  • Bug Report
  • Feature Request

Please provide the steps to reproduce the issue [Bug Report only]

image
in my angular 17 application i use nexted route. For that i need to use router-outlet on different component and imoport router-oulet com app layout and settings component. but when i use that . angular dev tools show an error
image
Injector error .

application ss
image

what is possible problem in nexted route. how can solve this.??

Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

Add router module as root on standalone project. or resolve chainedInjector.

Please provide a screenshot if possible [Bug Report only]

No response

Please provide the exception or error you saw [Bug Report only]

No response

Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

No response

Description [Feature Request only]

No response

Proposed solution [Feature Request only]

No response

Alternatives considered [Feature Request only]

No response

@JoostK
Copy link
Member

JoostK commented Jun 6, 2024

Please update to the latest Angular 17 release. You haven't provided information on which exact version you're using but there has been a fix at some point for this error.

@JoostK JoostK closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2024
@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 Jul 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants