• Use Node.js 18 in CI, fix JSDOM detection by@armanbilge in#75

Full Changelog:v1.1.0...v1.1.1

Contributors

• Updated to Scala 3.1.3

This release is functionally-equivalent tov0.2.0, and we consider the code to be production-stable at this point. Please share and enjoy!

This release is expected to be the final pre-1.0 release of the macrotask-executor project. It is fully source- and binary-compatible with0.1.0, and it is expected that 1.0.0 will retain this same property.

The primary changes from 0.1.0 in this release are support for Scala 2.11(!!) and polyfill support for the JSDOM test environment. The JSDOM environment was previously supported in terms offunctionality, but only due to the fallback tosetTimeout, meaning that all JSDOM usage was quite slow. Thanks to some creative sandbox breaking, we now utilize the Node.jssetImmediate function from the host environment when running under JSDOM, which allows for much higher performance (and thus, much faster tests!). This also allowed us to reenable the internal-facing regression tests which verify that the polyfill is in fact working and avoiding timeout clamping.

The primary expected changes between now and 1.0 will focus on testing in more environments (e.g. Safari on macOS) and any resultant hardening and bugfixing.

User-Facing Pull Requests

• #23 – Cross-build for Scala 2.11 (@armanbilge)
• #22 – MakeUndefined afinal val so that it can be constant-folded (@sjrd)
• #17 – Implement polyfill for JSDOM (@armanbilge)
• #15 – Add README reference about micro/macrotask queues (@armanbilge)

Thank you, everyone!

Contributors

Initial port and release of thePolyfillExecutionContext fromCats Effect! The code itself is already highly stable and well-tested, so we expect to progress towards a 1.0.0 very soon.

Very special thanks to@armanbilge for doing the lion's share of the work, particularly with respect to web worker support!

Contributors