You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
Angular 12
Description
Am updating angular 12 to 13 and updated all dependency package to its compatible version. Checked by giving npm outdated, no package is showing the version in red color. When given npm start, application url is getting launched but getting console error related to routing module as mentioned below
Minimal Reproduction
All the routing are correct, added RouterModule in AppModule and AppRoutingModule. Added in app component, added the path correctly in routing module.
Still the routing is not taking place, even it is not navigating to the error page, { path: '**', redirectTo: '/error' }
When i wrote console.log in resolver.ts and appcomponent.ts file, am getting those in console along with the mentioned error
Exception or Error
VM147 core.mjs:14757 NG0304: 'router-outlet' is not a known element:
1. If 'router-outlet' is an Angular component, then verify that it is part of this module.
2. If 'router-outlet' is a Web Component then add 'CUSTOM_ELEMENTS_SCHEMA' to the '@NgModule.schemas' of this component to suppress this message.
Console messages
MainAppComponent:constructor() - appcomponent.ts
BaseUrlResolver:resolve() - resolver.ts
I tried the same with node version 16.20.2 with npm 8.19.4, but getting peer dependency error for webpack-dev-server and typescript. When i try to update that, its throwing error as circular dependency, if am updating typescript, its throwing error for webpack-dev, so if am trying to update webpack, its throwing error on typescript
The text was updated successfully, but these errors were encountered:
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 angular.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.
Command
run
Is this a regression?
The previous version in which this bug was not present was
Angular 12
Description
Am updating angular 12 to 13 and updated all dependency package to its compatible version. Checked by giving npm outdated, no package is showing the version in red color. When given npm start, application url is getting launched but getting console error related to routing module as mentioned below
Minimal Reproduction
All the routing are correct, added RouterModule in AppModule and AppRoutingModule. Added in app component, added the path correctly in routing module.
Still the routing is not taking place, even it is not navigating to the error page, { path: '**', redirectTo: '/error' }
When i wrote console.log in resolver.ts and appcomponent.ts file, am getting those in console along with the mentioned error
Exception or Error
Your Environment
Anything else relevant?
I tried the same with node version 16.20.2 with npm 8.19.4, but getting peer dependency error for webpack-dev-server and typescript. When i try to update that, its throwing error as circular dependency, if am updating typescript, its throwing error for webpack-dev, so if am trying to update webpack, its throwing error on typescript
The text was updated successfully, but these errors were encountered: