Emelia Smith

@TimothyGu wouldn't backpressure with async iterator just be handled via something like: ```js const res = await fetch('https://httpbin.org/bytes/500000') for await (const chunk of res.body) { await doSomework(chunk) } ``` So...

Okay, so, an update from my end: We're publishing a fork with ReadableStreams as [@titelmedia/node-fetch](https://www.npmjs.com/package/@titelmedia/node-fetch), such that we can use it in our Cloudflare Worker development server. It's up to...

Oh, yes.. I forgot about that. The package description has it though.

This will need a build done on this branch, since you're committing the build artifacts to the repo too.

@holm I've just debugged this exact issue, and for us, it was because a header value included a `\n` / LF character, which the browser-ponyfill handles as being a new...

In the future, this will be better fixed by the `--staged` flag: https://github.com/npm/rfcs/pull/92/files

You could, but there's multiple ways of installing wasm-pack (I'd installed via Rust, not node packages) > On 12. Sep 2021, at 03:00, wleslie ***@***.***> wrote: > > Actually I'm...

I think I've a similar problem to this over on the typescript repo regarding installing a canary release: https://github.com/typescript-eslint/typescript-eslint/issues/5352#issuecomment-1188504561 I'm explicitly doing `npm install @typescript-eslint/parser@canary @typescript-eslint/eslint-plugin@canary` but npm is trying...

@schickling this is a duplicate of #16; It's arguable as to which is better.

For developer environments, you should probably just add your self-signed certificate to your operating system's certificate keychain; On MacOS, this can be done with: ``` sudo security add-trusted-cert -d -r...