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
{{ message }}
This repository has been archived by the owner on Apr 9, 2022. It is now read-only.
Here is a repo with the evidence. It's just an ng6 app created by CLI with one lazy loaded module, that doesn't compile. See readme for more info.
The log given by the failure
ng serve
ERROR in Could not resolve module app/lazyLoadedEvidence/lazyLoadedEvidence.module relative to /Users/Ricard/NG6Evidence/evidenceApp/src/app/app-routing.module.ts
Desired functionality
Typescript compiler should be able to resolve the absolute path described by Angular Router loadChildren property.
Mention any other details that might be useful
This was mentioned on some CLI issues
But analyzing the issue we can see its related to the scaffold typescript configuration, therefore it is related to schematics.
Heya, I'll answer this issue in angular/angular-cli#10673. It generally falls under the umbrella of a CLI issue and it's easier for other people to see the response there.
Bug Report or Feature Request (mark with an
x
)Area
Versions
Repro steps
Here is a repo with the evidence. It's just an ng6 app created by CLI with one lazy loaded module, that doesn't compile. See readme for more info.
The log given by the failure
Desired functionality
Typescript compiler should be able to resolve the absolute path described by Angular Router loadChildren property.
Mention any other details that might be useful
This was mentioned on some CLI issues
But analyzing the issue we can see its related to the scaffold typescript configuration, therefore it is related to schematics.
I guess the issue was introduced by this commit
The text was updated successfully, but these errors were encountered: