Was checking babel/babel#11478 and testing out syntax and noticed we don't error with the normal "use this plugin/preset" like we do for proposals with JSX itself. @nicolo-ribaudo mentioned it's probably since jsx is implemented as a normal plugin so we didn't have `this.expectPlugin("recordAndT

❌ to the ☕ script! ES6 is cleaner, more modern, and has a much more reliable linter—plus, people know how to read it—so we want to convert everything in the codebase. Most of the code is already there, but there are still specs written in Coffee.

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Problem

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

Proposed Solution

The project should switch to using the official [Redux

Are there any plans to submit SWC to the Kangax compatibility table. This is my (and I think most web developer's) goto resource when trying to determine which ES features a given project supports. It includes all common web browsers, as well as babel and typescript. I believe it also comes with a test suite.

https://kangax.github.io/compat-table/es6/ (+ the next version).

I would love to us

When applying FormField label styles (see #3998), for examplesize, the prop is being leaked to the DOM while it shouldn't.

Originally posted by @ericsoderberghp in grommet/grommet#3998

Not part of this review per-se, but we shouldn't be leaking `size` into the DOM.

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

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

This issue is a:

• Bug report
• Feature request
• Question / support request
• Other

The Testing Section of the documentation seems lacking. More specifically, the Example Test section does not provide an appropriate example test, since it doesn't even de

I've used Poi in the past to for Vue projects, but just recently decided to try it out with react. The current documentation is almost completely devoid of any hints as to how to get started. I ended up using an older version of Poi to get up and running.

I think if this project wants to keep up with the other framework specific tools it needs to atleast document what's changed since v9~

I k

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

legacyDecorators parser option should be documented.