[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

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

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