Babel

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

type FuncWithDescription = [
  function: (...args: any[]) => any,
  string: string
]

https://babeljs.io/repl#?browsers=defaults&build=&builtIns=false&corejs=3.6&spec=false&loose=false&code_lz=C4TwDgpgBAYgrgOwMYHUCWwAWARCBnJAJzTGDQHsEoBeKAbQCgooAzRJMygLigAoA

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

FormField component is missing reverse property in the type definitions although it works okay when provided

https://github.com/grommet/grommet/blob/00e0878202df5d7e0ae93bb2f2836c576f71c1eb/src/js/components/FormField/index.d.ts#L5-L36

Expected Behavior

No error

Actu

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