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
Error Application start, functional guard injection in the app_routes_config #54692
Comments
Hi, your code doesn't reproduce the issue. Could you try to provide a reproduction on stackblitz ? Also is your Guard comming from a library ? |
Not. It's the functional version of the framework's native guard. The project is very large, I encountered this error after upgrading angular to the latest version and integrating the new features offered such as standalone components. Please try checking here first for errors: app.config.ts
app.component.ts
app.config.server.ts
main.ts
|
At least |
The object relative to APP_INITIALIZER was commented but error continues. if you tell me what I can comment or change. The non-functional guard encounters the same problem.
|
I won't be able to help further without runnable reproduction. |
Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation. |
I add project on stackblitz. |
It's the same as in angular/angular-cli#27122. The path mapping for |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
router
Is this a regression?
Yes
Description
app.routes.ts
authentication.guard.ts
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: