Dealing with errors in Response streams?

I've encountered problems whilst attempting to stream Responses, and discovered that if an error is thrown within the stream it just seems to be completely swallowed.

Here's a simple example:

#!/usr/bin/env -S deno run --allow-net --watch

await Deno.serve(() => {
  return new Response(ReadableStream.from(content()));
}).finished;

// deno-lint-ignore require-yield
function* content() {
  throw new Error("EPIC FAIL");
}

#!/usr/bin/env -S deno run --allow-net --watch

await Deno.serve(() => {
  return new Response(ReadableStream.from(content()));
}).finished;

// deno-lint-ignore require-yield
function* content() {
  throw new Error("EPIC FAIL");
}

Hit the server and the request fails, but no errors are logged.

Is there a preferred way to handle the errors in a stream?
Or this is a bug in Deno? IMHO it feels like one, I wouldn't expects errors to just silently vanish like this.

Deno•17mo ago•

3 replies

Mark G

Dealing with errors in Response streams?

I've encountered problems whilst attempting to stream Responses, and discovered that if an error is thrown within the stream it just seems to be completely swallowed.

Here's a simple example:

#!/usr/bin/env -S deno run --allow-net --watch

await Deno.serve(() => {
  return new Response(ReadableStream.from(content()));
}).finished;

// deno-lint-ignore require-yield
function* content() {
  throw new Error("EPIC FAIL");
}

#!/usr/bin/env -S deno run --allow-net --watch

await Deno.serve(() => {
  return new Response(ReadableStream.from(content()));
}).finished;

// deno-lint-ignore require-yield
function* content() {
  throw new Error("EPIC FAIL");
}

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Deno

Chat about Deno, a modern runtime for JavaScript and TypeScript.

20,934 Members

Join

Dealing with errors in Response streams?

Dealing with errors in Response streams?

Continue the conversation

Deno

Continue the conversation

Deno

Similar Threads