Bug Report

Current behavior

No core-js polyfills in the final bundle.

Since babel/babel#10862 the core-js polyfill paths always have .js extension.
In shouldReplace function https://github.com/babel/babel/blob/41085248560b1403b8d0f99f108491e679531c6c/packages/babel-preset-env/src/polyfills/corejs3/entry-plugin.js#L52-L64
the module path is compared wi

https://github.com/jaretburkett/electron-icon-maker

Expected Behavior

Should be able to disable the DateInput while using typescript

Actual Behavior

If using typescript you will get an error that disabled doesn't exist on DateInput

URL, screen shot, or Codepen exhibiting the issue

Here is a link with someone stating the solution grommet/grommet#4438

Steps to Reproduce

Use the DateInput a

For the most part this just works, but functions within tagged markup get weird indent assertions, e.g.,

        ${collection.map((item) => {
          const { prop1, prop2 } = workWith(item);  // eslint: expected indentation of 4 but found 10 (indent)
          return html`  // eslint: expected indentation of 4 but found 10 (indent)
            <${Widget} prop1=${prop1} prop2=${prop2} />

See:
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0?type=dev

Validate the entire tree of options passed to preset.

Maybe, each plugin can export a list of options that only babili preset understands and we can validate them only when using the preset and not when using the plugin separately.

module.exports = function plugin() {};
module.exports.options = PropTypes.object({
  n: PropTypes.number
});

Or, this can be implemented in bab