Timo Tijhof

@D-Groenewegen I'm glad you found my advice from 11 years ago useful. Thanks for sharing that anecdote! I think the referencing of JavaScript global variables (jQuery in this case) is...

@mgol I'll look into if/when this worked. I'd certainly welcome it as a new feature, even if it wasn't there before. Today, one way to run multiple modules in the...

@NullVoxPopuli I wonder if a new assertion could help here? Something that would tolerate and/or expect a global error. The implementation could build on the (internal) `ignoreGlobalErrors` flag that we...

Yep, sounds good to me. I don't know about distributing ESM-only just yet, but definitely yes to Node 18+, and offering a native ESM export.

@david-pfx I'm interested in exploring this, and like the idea of allowing rich text formatting. This would unlock many interesting features. QUnit output is often passed through (or presented in)...

I don't think of QUnit as a library one is meant to bundle. Most test runners afaik share that sentiment, in that test runner generally act on your behalf to...

@NullVoxPopuli Yes, we have a Matrix room at (webchat), or via other clients: https://matrix.to/#/#qunitjs_qunit:gitter.im

I've done a bit more research as part of https://github.com/qunitjs/qunit/issues/1551 (ESM support) which is somewhat orthogonal to this. Apologies if you know this already, I'm mainly sharing here for future...

@NullVoxPopuli Cutting IE9 and IE10 sounds good to me. There hasn't been a semver-major yet, but definitely the next major release can simply cut these from the compiliation target! For...

Added to the roadmap. I expect that, this will naturally also break some other older mobile devices and desktop browsers, we can drop those at the same time (i.e. 5+...