Sergey Solovev

Found the reason and possible fixes. If the client sends the header `Accept-Encoding` with non-empty value, e.g. `gzip, deflate, br` (and it usually does), the production reverse proxy compresses response...

Have found out that the fix in question was moved to [release 2.0](https://github.com/django/django/blob/master/docs/releases/2.0.txt#L251), that is not ready yet. Currently, to get HTTP 1.1 responses in dev environment, I would suggest...

My deno.jsonc: ``` { "unstable": ["ffi", "cron", "http", "kv"], "tasks": { "cache_deps": "deno cache deps/**/*.ts && deno cache app/main.ts && deno cache app/dev.ts", "app_check": "deno fmt --check && deno lint...

Sorry about vague description. By “I can not use” I meant that vscode doesn’t like the “from” word of `ReadableStream.from([1, 2, 3])` expression and gives the following info in the...

If it helps, I shared my deno.jsonc in [this issue](https://github.com/denoland/fresh/issues/2371), it’s still the same.

Oh I see. I don’t have tripple slash comments in dev.ts. Removing the from main.ts doesn’t help with the issue.