Feature Request

• I would like to work on this feature!
  • If needs be, I can look into it

Is your feature request related to a problem? Please describe.

The JSX spec [1][2] lists } and > as invalid JSX text characters.

JSXTextCharacter :

• SourceCh

❌ 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

For historical reasons, the expectations object passed to t.throws() and t.throwsAsync() was not allowed to be undefined.

Now that we've simplified these assertions, we should allow expectations to be both undefined and null. See here:

https://github.com/avajs/ava/blob/55a3649000611900ba6dfbf94faefa6372a70e79/lib/assert.js#L76

This will cause some of our tests to fail, so th

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

I set

{
        test: /\.svg$/,
        loader: 'svg-sprite-loader',
        include: [resolve('./src/renderer/icons')],
        exclude: [resolve('./src/renderer/icons')],
        options: {
          symbolId: 'icon-[name]'
        }
      },
      {
        test: /\.(png|jpe?g|gif|svg)(\?.*)?$/,
        loader: 'url-loader',
        exclude: [resolve('./src/renderer/ic

I saw that many babel plugins used different ways to write their tests

I would have expected this handbook to propose at least one way to write unit tests, and if possible, ones that we can easily make run on a public CI such as travis.

Thanks

Spec: https://facebook.github.io/jsx/

Grammar:

JSXFragment :
    < > JSXChildren < / >

JSXChildren :
    JSXChild JSXChildren

JSXChild :
    JSXText
    JSXElement
    { JSXChildExpression }

That's means is say this is not correct ?

<> 
    <App2></App2>
    <> </>
</>

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

<Box border /> is a valid usage yet not documented. border="true" will apply borders to all sides.
https://v2.grommet.io/box?c=DwIQ9gHgUABDAmBLATgUwMYBdFgHYF4AiZMAd0NjiuuoCMxl5VlKAHAQ3iIFtUkBXbhQB8lUJBgcuhAM7d2AGwWEYtdugDWAcxL9c0+O2QaAtAGYVAelFxxESZx59EglWs06we6QsRaAFpjmVqLAluAQwkA#border

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

Was reading the the docs, and wanted to make use of the configuration mentioned here, with the nodejs apis.

But, I couldn't find any mention of it in the nodejs api docs. Had to do some digging into the source to see what was truly avail

This issue is a:

• Bug report

Description

Adding terser to nwb.config.js produces:

✖ webpack = 'terser'
  Unexpected prop in webpack config - see https://github.com/insin/nwb/blob/master/docs/Configuration.md#webpack-configuration for supported config. If you were trying to add extra Webpack config, try putting it in webpack.extra instead

Example nwb.config.js:

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

I'm submitting a feature request
I was fairly certain this was a thing, but it took me a long time to confirm to coworkers (and discover the nuances of using .babelrc vs. babel.config.js in the context babel-loader.

I think it's a good idea to document the fact that the config file is read automatically.

Is your feature request related to a problem? Please describe.
Users are unable to use console log lines in development mode.

Describe the solution you'd like
Update the documentation to demostrate how a user can disable console lines only for production builds.

Example babel.config.js

module.exports = api => {
  const babelEnv = api.env();
  ...
  const plugins = [];
 

I'm having an issue with the scss includes in my dependent packages for material-components-web and material-components-web-react. The sass is imported like this in their scss files... @import "@material/switch/mdc-switch";. The problem is that they don't add

Typing print() in the jscodeshift transformer triggers browser print dialog

To Reproduce
Steps to reproduce the behavior:

1. Specify to use jscodeshift
2. Type print() in bottom left corner
3. See the bug

Expected behavior
Shouldn't do that

Browser (please complete the following information):

• OS: OS X
• Browser Chrome
• Version 78.0.3904.108

**astexplorer

legacyDecorators parser option should be documented.

The features section in the docs states that nodemon is available in the project, when it's clearly not. It's not added as a dependency or as a command in the project. Maybe remove this from the docs or actually add nodemon?

The readme describes basic usage, but when the basic setup doesn't work, it's hard to know what to do.

There should be some command to run in order to test a simple import and get the search path printed, next steps in order to debug and/or similar.

I'm using this project and want to add mobx for state management.

I'm happy to PR documentation/example with some guidance!

Thoughts? @tirthbodawala