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
[ ] bug report => check the README and search github for a similar issue or PR before submitting
[ ] support request => check the README and search github for a similar issue or PR before submitting
[X] feature request
Current behavior
Current loaders and their dependencies cause bundle size on production environment to be increased dramatically (ex: http, lodash).
Expected/desired behavior
Publish each loader (except ConfigStaticLoader) in separate packages.
`ConfigHttpLoader
ConfigFsLoader
UniversalConfigLoader
And also, refactor ConfigMergedHttpLoader into
ConfigParallelLoader
ConfigSeriesLoader
or,
ConfigMergedLoader
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Angular version: 2.0.X
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):node --version =
The text was updated successfully, but these errors were encountered:
I'm submitting a ... (check one with "x")
Current behavior
Current loaders and their dependencies cause bundle size on production environment to be increased dramatically (ex: http, lodash).
Expected/desired behavior
Publish each loader (except
ConfigStaticLoader
) in separate packages.ConfigFsLoader
UniversalConfigLoader
And also, refactor
ConfigMergedHttpLoader
intoConfigParallelLoader
ConfigSeriesLoader
or,
ConfigMergedLoader
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Language: [all | TypeScript X.X | ES6/7 | ES5]
Node (for AoT issues):
node --version
=The text was updated successfully, but these errors were encountered: