Timothy Gu
Timothy Gu
@jimmywarting Unfortunately, async iterators don't provide a full replacement for streams with regards to things like backpressure. This is obviously a step in the right direction but there is still...
Hm, I guess I was more referring to the `highWatermark`-based backpressure. That does indeed work, yes.
What version of node-fetch are you using? I suspect this might have been fixed in v2.1.1.
@mfulton26 I don’t see a `redirect: "manual"` in your `fetch()` call. Did you miss adding it? If the response status code is 200, the `Location` header should not be modified...
@bitinn I meant in the OP, the response code is shown to be 200. I suspect before v2.1.0 the header was changed for the 200 case as well.
I think we can possibly just do away with the URL resolution. The user should have access to the request URL in the first place, and they can always do...
I think this is a good change if we can pull it off, with regards to the tooling and downstream review impact.
It looks like the same could be done for callback function types, which cannot be the type of any constant.
This could probably be cleaned up a bit, but I think it's still applicable.
The tricky part here is that we need to convert _V_ to the eventual target type (whether that be a union type as here, or a nullable type, or an...