upgraded to angular-router-loader for proper angular 6 code splitting… #670
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… and lazy loading support The prior approach with the older angular2-router-loader does not work anymore. We had to upgrade to the recommended angular-router-loader (see https://www.npmjs.com/package/angular-router-loader) and modify this webpack file accordingly. Works much better for us. In production, @ngtools/webpack does not work for us, and the proposed changes have been verified in prod and are stable.
|
rolling it back. This I think will break too many things for this project. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… and lazy loading support
The prior approach with the older angular2-router-loader does not work anymore. We had to upgrade to the recommended angular-router-loader (see https://www.npmjs.com/package/angular-router-loader) and modify this webpack file accordingly. Works much better for us. In production, @ngtools/webpack does not work for us, and the proposed changes have been verified in prod and are stable.
This requires the other change adding replacing the package in package.json