Jonathan Hall

> Should we take the opportunity to implement the `DriverContext` interface as well? But maybe that's a separate PR. I agree on both counts. It sounds like something we should...

> I would also propose to integrate it into the gopherjs tool itself as a `vet` verb Ah yes, good (and obvoius) suggestion. This makes me wonder, though... should the...

> I would also propose to integrate it into the gopherjs tool itself as a vet verb. I attempted to work on this today, but it's not quite as easy...

So we have the same problem with option #1... `gopherjsvet` ignores the `js` and `ecmascript` build tags by default. Which means that I'll need to re-implement `multichecker.Main` anyway, unless we...

> * Does GitHub actions provide us enough open source credits to run our relatively expensive test suite? Good question. I don't know the answer. > * Do they provide...

Your comment got me thinking... it would be strange for the actual compilation process to use `$GOPATH/src` in module mode... so makes me wonder if this is a problem with...

Indeed there is progress being made. Just a few hours ago, [a PR was merged](https://github.com/gopherjs/gopherjs/pull/1217) into our branch adding generics support. Of course, generics is a complicated thing to add,...

I suppose we should discuss how to label GopherJS 1.19, and what that means to the support of 1.17 and 1.18. What makes most sense to me, having not spent...

I think that's fine. So we'll have 1.17 (stable) and 1.19 (beta) under active support for the time being. No objections from me for merging/tagging 1.19-beta1.

> We will start to move our integrations into their own modules soon In that case, I have no objection (not that my vote would matter that much anyway :rofl:)...