node

With the introduction of web streams, it would be good to integrate support into the various common stream utilities...

Refs: nodejs/node#39134

/cc @mcollina @ronag

• stream.finished()

const { finished } = require('stream');
finished(new ReadableStream(), (err) => { /* ... */ });
finished(new WritableStream(), (err) => { /* ... */ });
finished(new Tr

Describe the feature you'd like to request

These are common issues developers run into with Next.js. Some are mentioned in the docs, but ideally you don't have to go check the docs.

Describe the solution you'd like

Instead, ESLint can provide compile-time feedback and suggestions.

• Trying to call an API route from inside getStaticProps / getServerSideProps leading to [next build

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

Describe the Bug

Hi. I've added a repeater interface for my JSON object, and set the fields as follows:
itemid: integer
quantity: integer

When requested from the API, the numbers are returned as strings. Example response:
[{"itemid":"3","quantity":"5","stackable":true}]

Note that the boolean type works correctly as opposed to integers.

To Reproduce

• Create a collection with

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