https://code.nasa.gov/

Maybe related to how the page causes a PROTOCOL_TIMEOUT?

From https://bugs.chromium.org/p/chromium/issues/detail?id=951684

Do you want to request a feature, a new application detection or report a bug?
new application detection

**Is your issue about WebExtension driver (Chrome & Firefox), the website, the NPM driver or the bookmarklet

Affected Projects
React

Is your feature request related to a problem? Please describe.
Was looking through the change log and the new documentation but could not find any reference to the deprecated DataController.

Describe the solution you'd like
Would be great to get some documentation on the recommended way to migrate from using DataController to not using it.

**Descr

On windows, mocha chokes on your test command. Use the following. The -- is necessary for windows batch wrapper

 "scripts": {
    "test": "./node_modules/.bin/istanbul cover node_modules/mocha/bin/_mocha -- -R spec"
  },

https://github.com/GoogleChrome/puppeteer/blob/v1.11.0/docs/api.md#class-coverage

Coverage gathers information about parts of JavaScript and CSS that were used by the page.

An example of using JavaScript and CSS coverage to get percentage of initially executed code:

// Enable both JavaScript and CSS coverage
await Promise.all([
  page.coverage.startJSCoverage(),
  page.coverage.

https://github.com/VictorBjelkholm/trymodule/blob/2030806d790213d426456959fdc7a69773a4c6f7/index.js#L59

Oh noes. Please don't. Never do string concat for commands, use execFile instead. Never pass environment variables directly to rm without sanitation, better yet, never spawn rm. Use a JS tools, like rimraf or even better del.

From: sindresorhus/awesome-nodejs#477

The protobuf "well-known types" (https://developers.google.com/protocol-buffers/docs/reference/google.protobuf) are included in every language runtime, including the npm package (see protocolbuffers/protobuf#1638).

Currently, grpcc requires proto files that import a well-known type to have a copy of the well-known type locally, otherwise you get an `Error: failed to import '...

Both the README.md and https://www.elm-live.com/ mention two flags --proxy-host and --proxy-prefix but the elm-live --help refers to them in camel case --proxyHost and --proxyPrefix. It appears that the camel case is the correct name which means the documentation is mistaken.

Took me a long while to notice this :(

At the very least, the rule used for those examples is deprecated, but the whole section could probably use a revamp too.