Babel

💻

• Would you like to work on a fix?

How are you using Babel?

@babel/cli

Input code

new class extends class {} {
  constructor() {
    super();
    return 3;
  }
}

[repl](https://babeljs.io/repl#?browsers=&build=&builtIns=false&corejs=3.6&spec=false&loose=false&code_lz=HYUw7gBAxgNghgZwREAPALiYATZtHIDeAvhIQFATQD2wC6ATgK5TrUMAUAlGZVRAiYAHEJy4BuPlQYh

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

Expected Behavior

defaultMode is used in Grommet component along with themeMode prop to determine initial theme mode between dark and light themes. As this property is used by Grommet Theme Designer, Grommet HPE Theme and in HPE Design System I would expect it to

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