ayame113 (val440)

Below are some additional refactoring suggestions from me. - There are currently three optional type definitions for parsers (`ReadOptions`, `ParseOptions`, `CsvStreamOptions`), but I think they can be simplified to one....

~~FYI, this issue seems to have been discussed in #5088 for a long time. Hopefully #17172 will resolve it I think.~~

Oh, I didn't realize you were talking about lsp here. Sorry for the noise!😓

That workaround works for me. thank you for your reply!

`https://api.deno.land/modules` now seems to return `{"message":"Not Found"}`. Sorry to ask again, but what if I want to get a list of all modules? For reference, we are trying to analyze...

I'm in favor of including features like `npm:comment-json` to std. I think `npm:comment-json`'s `parse` and `stringify` are consistent with the design of the built-in `JSON.parse`/`stringfy`, are easy to use, and...

Can this be reconsidered? For me, it's a bit annoying to ask the library author "sorry, please add `?target=es2020` to the import statements in your library" every time you run...

There are currently two types of CSV parsers/stringify: WebStream-based and non-stream (converting strings). As of today, it should look like this: ||string based|web stream based| |--|--|---| |**stringify**|`encoding/csv.ts`Can handle CSV with...

> @ayame113 Thank you for creating issue. We are planning to enable embedding of other notations as well, so we will consider this as well at that time. Thanks!

I think the disadvantages of the complexity introduced are greater than the advantages gained by implementing this. Since npm modules are designed with semver resolution in mind, having multiple versions...