tracking: Some modules cannot be marked as "browser compatible" because of outdated TS library types

[jsejcksn]

Context

The current browser compatibility CI test uses TypeScript's native DOM types when type-checking modules. This is appropriate.

However, the current DOM types appear to be outdated (technically, misaligned from what's being commonly shipped by browsers), so it's not possible to get tests to pass for some modules which actually are compatible in that sense.

Problem

The above described scenario prevents marking some modules as being "browser compatible" and prevents their discovery as such. I've included links to examples at the end of this message.

Candidate modules, grouped by related compiler diagnostic:

• ReadableStream lacks [Symbol.asyncIterator]() (missing in latest snapshot, updated 2022-03-18)
  Ref: refactor: mark modules as browser compatible #1972 (comment)
  Affects:

  • streams/merge.ts

• ReadableStream lacks any bytes & BYOB related typings (missing in latest snapshot, updated 2022-03-05, latest snapshot, update 2022-03-05)
  Ref: feat: streams based Buffer #1970 (comment)
  Affects:

  • streams/buffer.ts

• window.crypto lacks randomUUID() (missing in 4.5.5, available in 4.6.2)
  Ref: refactor: mark modules as browser compatible #1972 (comment)
  Affects:

  • uuid/mod.ts
  • uuid/v4.ts

[jsejcksn]

@crowlKats I don't see any activity at all in the TS repo which mentions ReadableByteStreamController. Am I missing something or should we file an issue?

[crowlKats]

yep, we probably should. Major missing structs are ReadableByteStreamController & ReadableStreamBYOBReader