You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, I really like what you've built with this library -- I've needed something like this numerous times and your implementation looks rock solid. 🙏
I mostly use Ava as my test runner of choice, and though Ava explicitly only supports node.js, I feel like the 95% use case could be supported in browser by something like polendina pretty easily by using a patched version of ava or something.
I'd personally definitely use this project if it supported ava.
Thoughts?
The text was updated successfully, but these errors were encountered:
This is something I'd need more info on. I've been interested in Ava but never actually used it, I was under the impression it did more than just Node.
I'm in the same boat here with node-tap - my ideal would be to use it for my projects but it's explicitly Node only and uses child processes and other Node-specific magic to get its work done and it's far too complex to consider a browser version (and it'd be chasing a moving target since they have no interest in it being browser compatible.
So, if you could figure out what it is that makes Ava Node.js-specific that would be a help, if it's something like sharding tests across child processes then it might be too complex to be worth the bother.
First off, I really like what you've built with this library -- I've needed something like this numerous times and your implementation looks rock solid. 🙏
I mostly use Ava as my test runner of choice, and though Ava explicitly only supports node.js, I feel like the 95% use case could be supported in browser by something like polendina pretty easily by using a patched version of ava or something.
I'd personally definitely use this project if it supported ava.
Thoughts?
The text was updated successfully, but these errors were encountered: