pipeline should immediately fail with ERR_STREAM_DESTROYED when any of the streams have already been destroyed.

Readable might need a little extra consideration since it's possible to read the data after being destroyed. Should maybe check _readableState.errored and/or _readableState.ended.

Refs: nodejs/node#29227 (comment)

These examples are currently not running locally.

• custom-routes-proxying
• with-compiled-css
• with-glamor
• with-mqtt-js
• with-reason-relay
• with-style-sheet
• with-styled-jsx-plugins
• with-web-worker

Expected Behavior

They're updated and working locally, with instructions included in the README as necessary 🙏

To Reproduce

C

e.g. isPassportNumber, etc.

https://docs.nodebb.org/installing/os/osx-mavericks/

Though we do have iOS devices for mobile testing, our core team doesn't actually own a mac (fight this war somewhere else :P). Would anyone with access to one mind testing and updating this page please? :)

More importantly the instructions for redis should be switched to mongo as it is our default recommended install; you can look at the

pnpm version: 5

Code to reproduce the issue:

not saved (you should add these dependencies to package.json if you need them):
@types/accepts link:node_modules/.pnpm/@types/accepts@1.3.5/node_modules/@types/accepts
@types/anymatch link:node_modules/.pnpm/@types/anymatch@1.3.1/node_modules/@types/anymatch
@types/argparse link:node_modules/.pnpm/@types/argparse@1.0.38/node_module

Context

This isn't really a feature request, as what I need is possible with nock as-is. But I spent several hours searching, reading old issues and searching through the source code to find the solution, so I thought this might help others.

I am testing code that accesses a service that sets the statusMessage of the response, as well as the statusCode. I am using nock to mock the server