Yoshiya Hinosawa

I was able to fix the issue if I changed the version to `0.0.6`, but I still see the same issue with `0.0.7`. I'll take a look in more details...

Oh, adding `import type { HandlerInterface } from "jsr:@hono/[email protected]/types";` resolved the issue for me, and if the issue once resolved, it doesn't reproduce even if I removed that workaround.. (BTW...

Tested with `0.0.8`. I still see the issue only after hitting `Deno: Restart Language Server` command, but if I changed anything in the file, that error disappears. I feel this...

> The problem may not be caused by hono, but by Deno's language server. Sounds true to me. If I check the script with `deno check` command, then the context...

I'm not sure it's good idea to implement this as TransformStream. No Deno API or Web API returns stream of streams or stream of iterables. The original comment of #4500...

I'm not sure `pLimit` is common abstraction of that situation/requirement. Could `Semaphore` class in this package ( https://jsr.io/@lambdalisue/async ) achieve that same thing? This issue ( https://github.com/denoland/deno_std/issues/4536 ) might be...

> As suggested by @BlackAsLight, I have removed line breaks handling from both encoder and decoder. I think this also works. In this case, we can remove/insert line-breaks before/after the...

I wonder if it makes more sense to put these APIs next to the `encodeBase64`/`decodeBase64` APIs in `@std/encoding/base64`. WDYT? cc @iuioiua @crowlKats

> I'd like to know more about any justifications for encoding/decoding streams. It's used for encoding/decoding a huge data, the size of which exceeds the memory limit of your program.

> We recently agreed to not have encoding/decoding + streaming APIs in the Standard Library as we thought there aren't many use cases. Can you link to the discussion?