Section/Content To Improve
Section "Config order of precedence".

Suggested Improvement
The current implementation of

Hello, we are the development team of VS Code extension for debugging React Native apps (vscode-react-native). whatwg-fetch package is used in React Native lib. In our extension we debug React Native apps as a Node.js processes. Node JS global context doesn't contain DOM modules, so "exports.DOMException is not a constructor" exception is g

If the document.domain property is set in the page, _has module throws error "Access is denied" when try to check window's property for example 'hasOwnProperty'.

So I think it is better to change _has module like below.

var hasOwnProperty = {}.hasOwnProperty;
module.exports = function(it, key){
  try {
    return hasOwnProperty.call(it, key);
  } catch(e){
    return 

There used to be only one type of operational error from node-fetch: FetchError.

This is no longer the case as I can count at least six: Error, NodeError, TypeError, SyntaxError, AbortError and FetchError. All of them can be triggered in one way or another through invalid response.

We would like to unify them in some ways but it's (a) a breaking change, (b) sometimes not standa

What is the current behavior?

Crawling a website that uses # (hashes) for url navigation does not crawl the pages that use #

The urls using # are not followed.

If the current behavior is a bug, please provide the steps to reproduce

Try crawling a website like mykita.com/en/

What is the motivation / use case for changing the behavior?

Though hashes are not ment to chan

• SerialPort Version: 6.2.0

• NodeJS Version: N/A

• Operating System and Hardware Platform: N/A

• Have you checked the right version of the api docs?: N/A

• Are you having trouble installing and you checked the Installation Special Cases docs? N/A

• Are you using Electron and have you checked the Electron Docs?: N/A

I have a device which is only intermit

From what I can tell, the ApiResponse objects can never have an undefined config.

Config is defined as optional here:
https://github.com/infinitered/apisauce/blob/master/apisauce.d.ts#L44
But is required here:
https://github.com/infinitered/apisauce/blob/master/lib/apisauce.ts#L200

URL : https://azu.github.io/promises-book/#race-delay-timeout

delay-race-cancel-play.js

copyOwnFromとTimeoutErrorの定義が重複している

Ahoy 🚢

The carryoverConcurrencyCount option could use some more verbose documentation. In toying with the package, it's not entirely clear what option value produce what behavior.

Perhaps even an examples directory that covered how this works?

Running DEBUG=emittery node x.js or DEBUG=* node x.js should output debug information/trace of events.

Events can be hard to debug, so this is important.

I'm looking for fee

Hello,

After recent update on latest typescript's (3.7.2) version I met following error. It happened on node 10.15.3 if it's important. Before update I used typescript (3.6.3) and vue-promised worked like a charm with it. Btw, it works similarly right now except below error.

<img width="1440" alt="изображение" src="https://user-images.githubusercontent.com/16149737/69920456-4ea1cd80-1499-11

I want to use GraphQL::Batch to load arguments for running mutations and it's not clear to me from reading the documentation if it is safe for me to use GraphQL::Batch.batch wherever I feel the need in my application. The note in the documentation refers only to using this in unit tests.

Can you provide clarification on whether GraphQL::Batch.batch can be safely used outside the test environmen

It'll be great to know what were the breaking changes between majors (is it safe to upgrade my projects or not) ?

Currently this information is only expressed in code changes, which is not very convienient

I guess it might be worth mentioning somewhere (eg requirements) that for vue-cli 3 this requires

{ compiler: true; }

in vue.config.js - see https://github.com/vuejs/vue-cli/blob/dev/docs/config.md

...to save other people the same head-scratching and frustration that I had.

Otherwise you'll get "You are using the runtime-only build of Vue where the template compiler is not av

Version 2 Checklist

Documentation

• Rewrite version 2 docs to reflect updates
• Rewrite version 2 docs in nuxt (and maybe markdown)
• Add guide for writing tests

Fixes

• allow data with DELETE
• Fix polluted params issue when where params send twice

Enhancements

• api renamed to http
• rename apiConfig to httpConfig

There is no documentation on how to set a timeout with the on function. I was looking through the code and can not seem to find it. I think there was before. It looks like this with removed with the removal of the global config in one of the later versions. I get "No ack for postMessage myEventName in http://localhost:8080 in 2000ms".

Please let me know if there is a way to set this timeout va