refactor: mark modules as browser compatible

[jsejcksn]

These modules are useful in browser environments.

[jsejcksn]

Are there even more that can be included in this PR?

[crowlKats]

@jsejcksn
streams/merge.ts
async/deferred.ts

[jsejcksn]

streams/merge.ts

@crowlKats It appears that the asyncIterator prevents compat for that module:

% deno cache --config ./browser-compat.tsconfig.json streams/merge.ts
Check file:///deno_std/streams/merge.ts
error: TS2504 [ERROR]: Type 'ReadableStream<T>' must have a '[Symbol.asyncIterator]()' method that returns an async iterator.
            for await (const data of stream) {
                                     ~~~~~~
    at file:///deno_std/streams/merge.ts:22:38

[crowlKats]

Then TS' typings are outdated. async iter on readablestream is part of spec

[jsejcksn]

Then TS' typings are outdated. async iter on readablestream is part of spec

@crowlKats I understand and agree, but the tests still fail and prevent inclusion until TS updates its DOM types.

[crowlKats]

Oh well, then we can skip on that one for now

[jsejcksn]

The same TS typings problem exists for uuid v4:

% deno cache --config ./browser-compat.tsconfig.json uuid/mod.ts
Check file:///deno_std/uuid/mod.ts
error: TS2339 [ERROR]: Property 'randomUUID' does not exist on type 'Crypto'.
  return crypto.randomUUID();
                ~~~~~~~~~~
    at file:///deno_std/uuid/v4.ts:30:17

[jsejcksn]

This PR turned out to be a bit bigger than I initially anticipated. Please review and let me know if I overlooked anything: thanks!

[kt3k]

Oh, we have many compatible modules! Nice work! @jsejcksn

[jsejcksn]

@crowlKats Is there a "todo" list in this repo's files/issues/etc. where the outdated DOM types issues mentioned above can be noted for revisiting after a future update to the TS DOM lib?

[kt3k]

@jsejcksn I don't think we have such issue

[jsejcksn]

@kt3k Can one be created? (Perhaps using the projects or wiki features if an issue is not appropriate — I realize many orgs don't leave issues open which are not yet actionable. However, it seems very useful to record this information in a way that increases the likelihood of its being seen again to be revisited.)

[kt3k]

@jsejcksn I think issue is the best for tracking it. Would you mind creating one?

[jsejcksn]

I think issue is the best for tracking it. Would you mind creating one?

@kt3k Done

[kt3k]

@jsejcksn Thanks! Nice!

[kt3k]

Modified the above issue a little bit, and made the remaining items into todo list (in github md notation). Feel free to edit them if you find any new items

[jsejcksn]

@kt3k I updated it again to sort at the top level by incompatible types, with affected modules listed under each, including links to the latest relevant lines in the TS DOM lib files.