Releases: mrhenry/core-web
v0.6.1
v0.6.0
Now includes DOMTokenList
and NodeList
polyfills from polyfill.io
.
These conflict with core-js
and require a change in your babel config to prevent issues.
+ exclude: [
+ "web.dom-collections.iterator",
+ "web.dom-collections.for-each"
+ ]
These need to be added in all steps/stages where core-js
|preset-env
might include these polyfills.
v0.5.2
- correctly exclude nested dependencies provided by Babel.
This increases build performance.
In most cases bundle size will also go down a bit.
v0.5.1
- update polyfill-library v3.107.1
- prevent automatic inclusion of polyfills with
// core-web-ignore @mrhenry/core-web/modules/<feature>
Biggest addition from polyfill-library is that all dependencies for Intl
features are now accessible from core-web (e.g. time zone data).
Better matchers and dependency configs for Intl
features and locales also makes it possible to use almost everything without manually importing things.
v0.5.0
NewExpression
matchersCallExpression
matchers
new Intl.NumberFormat('es', { style: 'currency', currency: 'EUR' }).format(number)
core-web will now detect usage of locale es
in the context of NumberFormat
and load all needed polyfills.
This is a breaking change because some features were previously matched by Identifier
(e.g. forEach
) and are now matched by MemberExpression
or CallExpression
.
although this should result in less false positives we want to be cautious.
v0.4.8
v0.4.8 (#547)
v0.4.7
v0.4.6
- polyfill-library v3.104.0
- various dependency updates
new polyfills :
Element.prototype.getAttributeNames
HTMLSelectElement.prototype.selectedOptions
v0.4.5
v0.4.5 (#377) * add Reflect.construct as an indicated depedency for custom elements * v0.4.5