• 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.

Maintenance release.

• updated dependencies
• crypto.randomUUID() is supported as of Safari 15.3

fixes for querySelector(':has(*)')

now passes all tests from WPT

support for querySelector(':has(*)')

following Safari's implementation

• polyfill-library v3.110.1
• crypto.randomUUID polyfill

• polyfill-library v3.109.0

• slightly better performance
• fix invalid browser version range for DOMTokenList.prototype.@@iterator

Better AST matchers for :

• Intl.DateTimeFormat
• Intl.DateTimeFormat time zone data

Better AST matchers for :

• document.visibilityState
• Event.hashchange
• Event.focusin
• Navigator.prototype.geolocation

provided by core-js and now excluded :

• globalThis
• JSON