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 was archived by the owner on Dec 3, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 3, 2023. It is now read-only.
it could be good to reduce bundle size, ie. load the first template the user hits into the bundle, precache the rest after the first page is already rendered.
It might also be able just to use normal webpack lazy-load syntax... but I haven't tried that yet.
You're right, html-loader does work for almost all cases. However, it would be nice for this plugin to have a story for when developers use ng-include to fetch external html fragments (and webpack would not by default put these html fragments in the bundle directory) or when they want to specify a templateUrl rather than template in their router or directives. This said, its still probably not a big deal.
Activity
jeffling commentedon Jun 9, 2014
it could be good to reduce bundle size, ie. load the first template the user hits into the bundle, precache the rest after the first page is already rendered.
It might also be able just to use normal webpack lazy-load syntax... but I haven't tried that yet.
scottmas commentedon Sep 24, 2014
You're right, html-loader does work for almost all cases. However, it would be nice for this plugin to have a story for when developers use ng-include to fetch external html fragments (and webpack would not by default put these html fragments in the bundle directory) or when they want to specify a templateUrl rather than template in their router or directives. This said, its still probably not a big deal.