v1.0.0

🎉 First major version 🎉

• no substantial changes from v0.7.8.
• API has been stable for a while now and is unlikely to change in the near future.

v0.7.8

• polyfill-library v4.4.0

v0.7.7

• update polyfill-library to v4.3.0

v0.7.6

Add support for browserslist
It is now possible to re-use existing browserslist config from your package.json or pass a config via the browserslist plugin option.

/* babel.config.js */
module.exports = function(api) {
	api.cache(true);
	return {
		plugins: [
			["@mrhenry/core-web"]
		]
	};
};

v0.7.5

update to polyfill-libary v4.2.0

v0.7.4

• polyfill-library v4.1.1
• improvements to querySelector polyfill selector parsing

v0.7.3

• querySelector(':HAS(> img)') now works with upper case :has()

v0.7.2

• querySelector(':has(:has(any))') must not throw an Exception

v0.7.1

• fix temporary attributes not being removed in element qsa polyfill

v0.7.0

• remove Intl. polyfills
• disallow nested :has : fixes #976
• update polyfill-library to v4.0.0 (drops IE 8 support)

---

Intl. polyfills are a poor fit for core-web because automatic injection doesn't align with how the feature is used.

Either authors want a dynamic codebase with support for any locale.
In this case they would use variables, which we can't handle as we can't infer the needed locale files from that.

Or they want a single locale to have access to formatters.
In that case they are better off importing formatjs directly.

In polyfill.io it does make sense to include Intl as you can more easily dynamically load the correct locales based on client side values/preferences.

Removing Intl has massive benefits as it reduces the package size and speeds up the AST matching.