Differentially loaded polyfill naming is confusing #13808
Labels
area: @angular-devkit/build-angular
feature
Issue that requests a new feature
freq1: low
Only reported by a handful of users who observe it rarely
severity1: confusing
Milestone
🚀 Feature request
Currently the differentially loaded polyfills are named something like this:
es2015-polyfills.93d33834f014c18240da.js
polyfills.13391cdb066748d88c83.js
These names are a little confusing because one might guess that the es2015 one is loaded by modern browsers, and the other one is loaded by legacy browsers, but this isn't what happens.
Today, the
es2015-polyfills.js
is loaded by browsers that DON'T support ES2015, and the file marked ES2015 is ACTUALLY ES5.Proposals
I propose to instead name the legacy file based on what it contains in a way that makes it clearer by using an additional file extension. The modern one can stay the same this way.
polyfills.es5.js
- Contains ES5 and is intended for older browserspolyfills.js
- Contains modern JS and is intended for modern browsersThe text was updated successfully, but these errors were encountered: