ehmicky

Allow multiple readers to iterate over a stream at the same time

2

### What is the problem this feature will solve? When multiple callers use [`Readable[Symbol.asyncIterator]`](https://github.com/nodejs/node/blob/4c3e9659ed116e610d8da8aa0b692cc8c6abb6e4/lib/internal/streams/readable.js#L1336), each caller receives a partial result. ```js import {Readable} from 'node:stream' const stream = Readable.from(['a', 'b',...

Pipeline errors are not properly handled in Gulp v5

5

Before you open this issue, please complete the following tasks: * [x] use the search bar at the top of the page to search this repository for similar issues or...

### Reproduction [TypeScript playground](https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbwM5gIYHcB2BfOAzKCEOAckwgBMBTALgGMALYAGwoH0xC6qkkSBYAFChIsOACIAAlCohgADwC0UAK6YA9OWrihQlBkwAKElUYQSAGjgBtE-NThmVEgF0rCKpgBuNRAFEADQBBAFkABQAZP187BzAnEmxsAEoAbiA). ```ts import {spawn} from 'node:child_process' import "@remix-run/node" spawn('echo', ['example'], {env: {EXAMPLE: 'example'}}) ``` Gives the following type error (only if `@remix-run/node` is imported): ``` No overload...

We should add a link to [`nano-spawn`](https://github.com/sindresorhus/nano-spawn) once it's stable.

Wrong `state.json` is being used

5

This was initially reported by @biilmann. He created a completely fresh project with just a `public` folder, a `functions` folder and a `netlify.toml` file and then did a `netlify deploy...

**Describe the bug** If a request has no `Accept-Encoding` request header, the response will not be compressed by `@middy/http-content-encoding`. If that response is cached, then another request with an `Accept-Encoding`...

**Is your feature request related to a problem? Please describe.** In `@middy/http-content-encoding`, if the `Cache-Control: no-transform` request header is set, the response should not be compressed. **Additional context** The [standard](https://httpwg.org/specs/rfc9111.html#cache-request-directive.no-transform)....

**Describe the bug** By default, `@middy/http-cors` sets the `Vary: Origin` header, which is good. However, it only does so based on whether the `Access-Control-Allow-Origin` request header has been set and...

**Describe the bug** `@middy/http-cors` sets the following HTTP response headers: `Access-Control-Request-Methods` and `Access-Control-Request-Headers`. https://github.com/middyjs/middy/blob/f50d2352be04a92ce8e6352d70d218242f714633/packages/http-cors/index.js#L154-L165 However, the correct spelling of the former header is [`Access-Control-Request-Method`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Request-Method) (no `s`). Additionally, those headers are...

**Is your feature request related to a problem? Please describe.** `@middy/security-http-headers` is using the `Report-To` HTTP header, which [has been deprecated](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Report-To) in favor of the [`Report-Endpoints`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints) header. **Describe the solution...