James Garbutt

makes sense. from a quick look, i can see the whole `use(...)` concept will make it difficult - allowing patching of the exported module by third party packages basically. won't...

@keithamus something like #1498 maybe (based in 5.x.x branch fwiw) good if some day you and/or the other maintainers get chance to have a stab at that, or help finish...

@abdonrd it is here: https://github.com/parse5/parse5-tools and published on npm under `@parse5/tools`. iirc the lit repo now uses it the modernweb PR went stale, i think thanks to a lower activity...

@abdonrd not anymore, good spot! i feel like an idiot now :D totally didn't realise. the package had been published but not the repo

have you considered 8.x being your first esm-only version of rxjs? seems to me it is the ideal opportunity to do that. we're now at a point where most consumers...

i think i figured most of it out now, got our test run down from ~15 minutes to ~6 minutes with the following: ### Parallel computation (minor) [this loop](https://github.com/modernweb-dev/web/blob/1eb5345267e59fbcd6054064a4ccdb412b826711/packages/test-runner-coverage-v8/src/index.ts#L47) runs...

@Westbrook weirdly using an lrucache with a `max: 200` took it down to 4 minutes rather than 6! witchcraft seems like a good option then. i suppose we should be...

@web-padawan i roughly understand it and have most of it in #2050 but could do with help getting it completed it is an incomplete solution right now. i got a...

@benlesh fyi this seems to have also caught some leftover dtslint assertions for things that have since been removed e.g. `every` supporting a `thisArg` the jsdoc was also mentioning those...

any chance you can take a look at this @benlesh ? 👀 low priority ofc, assuming you do want the change!