will try that, thx
@dnolen ran into this issue while building nextjournal with latest master, which I guess is a blocker. unfortunately I don’t think it would be easy to add a test for that, right?
@kommen ... yeah not so easy to test for
one idea - puppeteer is pretty solid - might be nice for some community written tests along these lines
mhm. actually, the issue was caught by our own puppeteer tests
it just feels like a bit of work to setup puppeteer tests for something that we'd normally see before a release
REPLs often catch this kind of thing, but the module stuff is a bit of an outlier because it's a build feature but needs a browser to test
still GCL has been changing at a faster pace than in the past so if this keeps happening I'm not against it