Babel

💻

• Would you like to work on a fix?

How are you using Babel?

Programmatic API (babel.transform, babel.parse)

Input code

export default interface {}

[REPL](https://babel.dev/repl#?browsers=ie%2011&build=&builtIns=false&corejs=false&spec=false&loose=true&code_lz=KYDwDg9gTgLgBAE2AYwDYEMrDgSwHYzBQBm6y2A3gL4DcQA&debug=false&forceAllTransforms=false&shippedPropos

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

Expected Behavior

react-desc should be removed from grommet and the documentation for each component should be contained in the grommet-site repo.

Original discussion about removing react-desc #2976

Actual Behavior

Grommet is using react-desc for documentation and the docs are in the grommet repo

Steps:

In the steps below replace with the name of the comp

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