Description
Bug Report or Feature Request (mark with an x
)
- bug report
Command (mark with an x
)
- build
- [x ] serve
Versions
NPM 6.2.0
Node v10.9.0
Angular CLI: 6.0.8
Node: 10.9.0
OS: win32 x64
Angular: 6.1.4
Package Version
@angular-devkit/architect 0.6.8
@angular-devkit/build-angular 0.6.8
@angular-devkit/build-optimizer 0.6.8
@angular-devkit/core 0.6.8
@angular-devkit/schematics 0.6.8
@angular/cli 6.0.8
@ngtools/webpack 6.0.8
@schematics/angular 0.6.8
@schematics/update 0.6.8
rxjs 6.2.2
typescript 2.7.2
webpack 4.8.3
Repro steps
-
To simulate this you have to download source code here (because stackblitz cannot even generate working, ready to download solutions...):
load-children-issue.zip -
NG serve = error:
ERROR in Could not resolve module ../../room/room.module relative to /D/GIT/angular-empty/bara2/src/app/layout/layout.module.ts
if you check layout.module.ts, routing is imported via index.ts files - importing layoutRouting (layout.routing.ts)
BUt it works when you resave anything (when project is rebuilt on watch. )
Expected behavior
There should be no problem with index.ts files regarding the relative path in loadChildren.
Desired functionality
LoadChildren relative path shoudl work regardless the folder "deepness"