The dom lib is missing typings for ReadableStream.from

[BlackAsLight]

Version: Deno 1.39.4

Really just forwarding this comment since that issue is closed and therefore seems to not be on anyone's radar.
#21733 (comment)

Example

This code runs successfully, but throws a typing error on .from

function* example() {
	yield 1
}

const stream = ReadableStream.from(example())

for await (const value of stream)
	console.log(value)

{
	"compilerOptions": {
		"lib": [
			"dom",
			"deno.ns"
		]
	}
}

[kt3k]

We usually don't update lib.dom.d.ts with our own modification, but directly follow the updates from TypeScript repository. Should this case be considered as an exception? cc @dsherret @bartlomieju

[kt3k]

A feature needs to be supported by two or more major browser engines to be included here, to make sure there is a good consensus among vendors: Gecko (Firefox), Blink (Chrome/Edge), and WebKit (Safari).

https://github.com/microsoft/TypeScript-DOM-lib-generator

lib.dom has the above criteria to include new APIs and ReadableStream.from doesn't meet it yet (ReadableStream.from is only supported by firefox)

[Hajime-san]

It's a temporary measures that overwriting deno.web next in dom to lib array.
But, there is a possibility to cause other typing issues...

{
  "compilerOptions": {
    "lib": [
      "dom",
      "deno.web"
    ]
  }
}

BTW, it's not only Readable.from problem but other APIs that is not implementing commonly?