[Given REPL](https://babeljs.io/en/repl#?browsers=&build=&builtIns=false&spec=false&loose=true&code_lz=MYGwhgzhAEBCkFNoG8BQ1rAPYDsIBcAnAV2Hy0OgAoA3MEAShXQ2nwAsBLCAOjpGgBeaPwDcLAL4sA5gnxsEBKkzStohOcUI42XXmMmopqUJBgB5AEYAraAgAe-BDgAmMeBCSrMuAiTIU1PwqLBgQxAAOCIS09AyGGAD0idDmNNGEnC5IsvhOlGCu0MSe0OFRhDJyCkohahr4Wjrl0TxOBOIYUsbYePJYNkLQOAgA7qk2VETECAzivRBYIAg8IFjSVAPWbYr4cya-Sytm0fibNjsEADTQAOQAkjRYANac

❌ 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

https://twitter.com/TheLarkInn/status/1056729742437543936
https://github.com/reactjs/rfcs/blob/gaearon-patch-2/text/0000-lazy.md

Describe the issue / bug.

I added these configs in launch.js,

After F5 debug, already vscode debugging child processes.

but, breakpoint in main process used in folder

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

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.

• I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.

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

DESC

在v2.2.12版本上，通过 thinkjs plugin xxx 创建的插件，在经过babel编译时存在问题，编译后的代码，无法在thinkjs系统中使用，其依赖和编译命令为：

 "dependencies": {
    "babel-runtime": "6.x.x"
  },
  "devDependencies": {
    "mocha": "1.20.1",
    "istanbul": "0.4.0",
    "babel-cli": "6.x.x",
    "babel-preset-es2015-loose": "6.x.x",
    "babel-preset-stage-1": "6.x.x",
    "babel-plugin-transform-runtime": "6.x.x",
    "ba

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

I like your project a lot. I've been using it for a couple of months now. Just the demo folder never felt natural for me.
Simplify the project by integrating storybook instead of the demo folder.

then users can create documentation of their components.

I think it will benefit all library authors for React/Preact/ vue/ even javascript.

[Storybook](https://git

You might already know backpack or pocky which are kind of Poi for back-end (Node.js) apps.

So what about we making it possible as a poi preset 😄

But note that here we don't need the default poi command, since we don't need that dev server. Instead we use poi watch & nodemon to develop the app, each time webpac

I couldn't find any place in the documentation that would showcase all possible configurational parameters that can be used inside backpack.config.js file. Is it possible to add not only config.entry.main but also showcase all other available options with a brief explanation of its purpose?

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.

First of all, congrats on the great project!
I've started using it a couple of days ago but I've now started to bump onto some very big hurdles due to the fact that the Readme and all of the currently available documentation is scattered across several docs, the micro bundle project and so on.
I'm afraid this issue will end up being kind of redundant but I was unable to find anywhere else where

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

Since probably 90%+ of the users will want to have Babel and the autoprefixer it would be nice to ship a preset (using group()) that sets some blocks configured in a best-practice manner:

• Babel with babel-preset-env (target last 2 versions for instance)
• PostCSS with autoprefixer (similar target as set for babel-preset-env)
• Set process.env.NODE_ENV (in output code, using `defin

/* example.ts */

// error: Parsing error: Unexpeced token, expected ":"
interface example {
  readonly id: string;
//         ^
}

/* .eslintrc */
{
  "root": true,
  "env": {
    "es6": true,
    "node": true,
    "jest/globals": true
  },
  "parser": "babel-eslint",
  "extends": [
    "eslint:recommended",
    "plugin:prettier/recommended",
    "plug

VSCode not giving auto suggestions of file name inside the directory once we are using alias name with babel module resolver plugin for react native .
I am having .js file inside the path @components but it is simply giving the suggestion as
@components/ showing the suggestion as {} react,{} props,{} react-native

My .babelrc file :
{
"presets": [
"react-native"
],

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?

Under branch 10-player-input, inside app/index.css, https://github.com/tylermcginnis/react-course/blob/10-player-input/app/index.css:

Under this btn class: text-decoration: uppercase; should have been text-transform: uppercase;

.btn {
  padding: 10px;
  text-decoration: uppercase;
  letter-spacing: .25em;
  border-radius: 3px;
  border: none;
  font-size: 16px;
  display: f

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