Meta: downstream issues

[annevk]

We'll file issues against Deno and Node.js, but presumably we should also file an issue against https://github.com/w3c/webidl2.js. And potentially against https://github.com/web-platform-tests/wpt as idlharness.js does not use the new webidl2.js automatically. Is https://github.com/plinss/widlparser by @plinss what @tabatkins's https://github.com/tabatkins/bikeshed uses? Do both of those require an issue or just the former?

Once we have a list of places to file issues against I can make the necessary changes to whatwg/spec-factory and whatwg/meta.

cc @saschanaz @dontcallmedom @foolip

[plinss]

Bikeshed uses widlparser, so most WebIDL changes need only be filed on widlparser (unless you're adding a new high-level concept in which case you'll need issues on both).

[tabatkins]

Well, if there are updates to widlparser Bikeshed won't catch them automatically, since I pin versions. But I do pay attention to widlparser so it should be fine.

I only need a Bikeshed bug if it's something that'll mean a new type of definition, or changes to how I do autolinking or something (like the new "static and non-static can reuse names" behavior that was recently accepted).

[annevk]

PRs created to resolve this. Thanks for the advice!