-
Notifications
You must be signed in to change notification settings - Fork 12k
Closed
Labels
needs: investigationRequires some digging to determine if action is neededRequires some digging to determine if action is needed
Description
Versions
Angular CLI: 1.5.0
Node: 8.9.1
OS: win32 x64
Angular: 5.0.5
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router
@angular/cli: 1.5.0
@angular-devkit/build-optimizer: 0.0.34
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.38
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.8.0
@schematics/angular: 0.1.8
typescript: 2.4.2
webpack: 3.8.1
Repro steps
- Checkout the project : https://github.com/arnaudoisel/lazy-loading-routes-bug
- > yarn (or npm install)
- > ng serve
- Modify the "routes.ts" file (by adding a comment for example)
- Save the file
=> The warning will be displayed in the console
Observed behavior
With Angular CLI, if a project contains a module that is lazy loaded, when we modify the file containing the routes, after the automatic rebuild by Angular CLI, the following warning message is displayed in the console :
WARNING in Duplicated path in loadChildren detected during a rebuild. We will take the latest version detected and override it to save rebuild time. You should perform a full build to validate that your routes don't overlap.
Desired behavior
Desired : No warning message displayed in console.
Otherwise it might cause bugs while developping. And even without any real issue, the warning message is a bit scary and could prevent from acknowledging real bugs in the application.
tmakin, mfahlen, sjswoboda, benelliott, LastDragon-ru and 23 more
Metadata
Metadata
Assignees
Labels
needs: investigationRequires some digging to determine if action is neededRequires some digging to determine if action is needed