Ryan Tsao

Both [Node's V8 inspector](https://chromedevtools.github.io/devtools-protocol/v8/Profiler/#method-startPreciseCoverage) and [Chrome](https://chromedevtools.github.io/devtools-protocol/tot/Profiler/#method-startPreciseCoverage) appear to support the Profiler domain (including support for `startPreciseCoverage`) I tested coverage reporting with node v8 inspector and Canary Chrome DevTools but it...

In implementing https://github.com/rtsao/unitest/pull/30, when dealing with standard promises instead of async functions, it appears unhandled promise rejection stack traces in Chrome via the remote debug protocol is much better than...

Any feedback @alexander-akait @TheLarkInn ? This would be nice fix to get landed

In practice, it might be nice to configure webpack to assume all modules are side effect free by default, as the whole npm ecosystem doesn't use it yet. If webpack...

It would be nice if the entire npm ecosystem adopted the sideEffects package.json field, but realistically, I think it will be a long time before that is the case. Consider...

As a workaround for the old version of Jest being used in CI for Node v10, I've updated this test to only use `it.failing` if the API is found. This...

As a heads up, I might start implementing this. I think the config proposed by @rauschma sounds good.

Created a PR for this: https://github.com/babel/babel/pull/6731

The original issue doesn't really talk about it, but I think this is a nice feature for library authors.

> Thanks for working on this. Unfortunately the CI is failing. I see, I was just running `cargo test` locally (CI had to be manually enabled on this PR). There...