-
Notifications
You must be signed in to change notification settings - Fork 12k
Initial dynamic import support #9515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
2d8eec2
to
2f4c8f5
Compare
2796f86
to
db6554e
Compare
db6554e
to
7192c72
Compare
Hello clydin, Regards, |
You need to use the module factory to create a module reference which in turn can be used to create component factories for the module's defined entry components. Components are not loaded independently. |
yes, we are currently doing it by hacking the loadchildren of route module, which creates a chunk which contains ngfactory of lazy module and all the referenced component's ngfactories. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This adds the
additionalLazyModules
option to theAngularCompilerPlugin
which allows a developer to add support for additional lazy modules not found via static analysis of the router configuration.Also adds a
lazyModules
option to the app section of.angular-cli.json
. Paths are relative to the applicationsroot
configuration option.Example Component:
The module path passed to the
load
method should be the full name of the module specified in the application configuration plus the#
separator and class name from the file; or nothing additional for the default export. This is the same format that theloadChildren
router configuration option uses.