-
Notifications
You must be signed in to change notification settings - Fork 12k
Provide a way of enabling differential loading only on certain builds #14602
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
Comments
Browserslist already has a feature called "environments", see here: I tried to use it to create a "development" environment where no ES5 version is built, only to realize that neither BROWSERSLIST_ENV nor NODE_ENV influences the way the angular build system loads the browserslist file. Please help! |
Experiencing same problem, spending additional 30 seconds and 15 mb on building es5 bundles that would never be used on dev envs, waiting for this feature to be added very much |
For Angular v10 a new |
I think that's a schematics option only, if I understood the commit correctly it just controls what gets put into the browserslist file when creating an application. i.e. you can't do |
This issue is now obsolete since differential loading will be removed in the next major version. See: #21467 |
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. |
🚀 Feature request
Command (mark with an
x
)Description
Currently
browserslist
is used to determine whether to create an es5 build as well as es2015. However that is global for the whole project, what I'd like is a way to only build an es5 version on our production environment, our staging environment already takes ~20 minutes to build, building an es5 version is only going to make this build time longer and all of our staging users are on modern browsersDescribe the solution you'd like
To allow forcing differential loading for certain builds in
angular.json
via thees5BrowserSupport
flag. Currently it only has an effect on the polyfills and not whether an es5 build is created.Describe alternatives you've considered
There are no arounds AFAIK
The text was updated successfully, but these errors were encountered: