Khải

@chyh1990 Either way is fine to me. This is a choice for you — the maintainer to make. In my opinion, the first choice would make switching between implementations easier,...

Deno treating `video/*` media types as TypeScript is weird to me.

@jsejcksn I have created https://github.com/denoland/deno_website2/issues/1732, you may continue the discussion there.

> This could just type strip or perhaps also transform down to ES6 for compatibility reasons (or maybe some query parameter to specify the target). For now, compiling TypeScript to...

> Bundling as one JS file should be optional, sometimes I want just couple of neat functions from functional libraries and not all. My wish was and still is for...

If I understand correctly, `npm:` scheme can only be used when a local `node_modules` directory exists, which mean libraries that are published in `deno.land/std` and `deno.land/x` shouldn't use it. I...

It seems that you're busy. Notify me by `@` mention when you're done.

@ulises-jeremias I'm just too lazy to do a throughout review. Plus, it's not really my use case (my CI generates `PKGBUILD` before feeding it to this action), so I'm not...

The feature I desire most is **security without inconveniences**. In VS Code, many extensions are inherently insecure since they could execute arbitrary code from a cloned project. For example, rust-analyzer...

@theAkito The plugins would be in WASM, so you can use any language that compiles to WASM. I think making the API too open would make it hard to avoid...