node-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see whatwg/fetch#67)

On other hand, we have a fetch-node specific extension to limit the size of the response.

My prop

Summary of Problem

Not able to open port with stopbits as 1.5

I am currently building a desktop client using electron, where the COM port receives data correctly for values: baudRate: 2400, dataBits: 7, stopBits: 1.5, parity: 'none'

I found from the node-serialport documentation, stopBits Must be one of these: 1 or 2. But, should 1.5 be supported as well? especially for old & slow

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の定義が重複している