Ben Keen
Hmph, sorry! Bumping to next release again. Need to get 3.2.6 out tonight.
Hey @Shabasha, sorry for not responding sooner! No worries, I'll release a patch release to address this. In the meantime, you can safely just remove these lines in your `library.php`...
Hey folks! We just encountered this same issue. We'd just upgraded to jest 29 and axe-core 4.7.0, from jest 26 and axe-core 4.4.3. I'll need more time making real sense...
A little more info. In our case it's due to the DOM content in the problematic tests being particularly large. It doesn't appear to be the specifics of the DOM...
To be clear, this isn't a parallelism issue - keeping it sequential is totally fine. When this problem occurs for us (it's still an issue) it's just because the previous...
Well, yes and no. I ended up upgrading our monorepo piecemeal - updating the packages to the latest jest that didn't have axe tests first, then doing them last. In...
Closing, out of date.
Thanks @chengcyber and everyone! Excited to give this a go. :)
Just FYI, it's working very well @chengcyber! Just one little thing. I found that when I had a patch file already created, re-running `rush-pnpm patch-commit` with new changes had no...
Actually I'm going to move all doc to github pages. Not as pretty but simpler, more manageable and familiar for everyone.