Since we are now only building Babel on Node.js 14 (even if we still test it on Node.js 6), we can use native ECMAScript modules for the build scripts:

• Top-level scripts
  There are a bunch of scripts/tests in the scripts folder: they can probably all be rewritten to ES modules.
  We can probably add "type": "module" to the top

Add weight property to the Anchor component, similar to how Text has it.

This is an ask from the CCS team.

It would be nice to have a babel macro that automatically runs the babel plugin to remove the runtime. That way, this project would work out of the box with "zero" config tools like create-react-app.

I'm thinking it could be something like:

import {html} from 'htm/preact/macro'

This is similar conceptually to CSS-IN-JS libraries providing a macro for their tools. See https://e

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