Brian Crowell

fetch-mock Response.body is not always a stream in Node.js

2

[WhatWG fetch API spec](https://fetch.spec.whatwg.org/#body-mixin) requires that Body.body is of type ReadableStream. node-fetch [interprets the standard](https://github.com/node-fetch/node-fetch#bodybody) as requiring a Node.js Readable stream. fetch-mock [returns a Buffer](https://github.com/wheresrhys/fetch-mock/blob/4b54e6db42a3e87700ef37a27a7a4d7df29cb3d7/test/server-specs/server-only.test.js#L16) if anything other than a...

This is not a great fix; it ignores that method is only inspected when it's in the first fetch() parameter, and it glosses over the fact that the navigator object,...

FIX: fetch-mock Response.body is not always a stream

2

The WhatWG fetch spec requires that Body.body (and therefore Response.body) is always a readable stream, but it doesn't always happen that way in Node. This seems to be because ResponseBuilder...

fetch-mock has a function [patchNativeFetchForSafari](https://github.com/wheresrhys/fetch-mock/blob/2f6464c5a678ed7dd25e54d4956d0ea7088c1a3e/src/lib/fetch-handler.js#L24) that wraps the native fetch when it detects it's running in Safari. By a funny coincidence, what fetch-mock looks for is exactly how [jsdom identifies...

Failure on web client when using browserify + ws 1.1.0

3

I don't know what exactly the failure is; maybe it's because ws 1.1.0 doesn't include the client side anymore? Whatever the reason, trying to use angular-websocket 1.1.0 on the client...

Published types aren't complete enough for Pyright/Pylance

9

It seems a bit unfair to file this as a "bug," when really what's going on is that the Python community is trying to figure out what a "typed" Python...

KEY_OVER_1024_CHARS error with large indented blocks of comments

4

**Describe the bug** If there's a large block of comments hanging indented under a key, that can trigger an error suggesting that the next key indicator is too far away....