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
The patterns encouraged by this package are awesome, but they are only as good as the tools that support them.
The use ofimport.meta.url in the analysis has limited support in build tools and test frameworks. For example in this project's own tests, import.meta.url can't be used due to the CommonJS conversion used in Ava. I thought it could be useful to create an issue to track support for popular test frameworks? Let me know if that sounds like a sensible approach.
Check to see if Parcel's default handling of Worker functions correctly with this
Feedback welcome if alternative approaches are preferable too - I don't want to make more work than necessary, but it does also seem a useful thing to do so far as it isn't too much effort to track these (and in theory the modules support naturally in these projects should align with these directions).
I was trying to test a repo I had using Ava, one of the packages used web-worker deep within and Ava had an error with that. I migrated everything to Mocha, and it seems to work. Perhaps you may check the box for Mocha.
Activity
developit commentedon Apr 14, 2020
Here's a quick Babel hack that should make it work in Webpack.
[-]Tracking test framework / build tool support[/-][+]Test Framework / Build Tool Support[/+]pedrorafa26 commentedon Oct 22, 2021
Hi I'm facing thi issue, but I don't know how to implement this Babel hack into my project, Could you help me with the implementation?
erhant commentedon May 4, 2023
I was trying to test a repo I had using Ava, one of the packages used web-worker deep within and Ava had an error with that. I migrated everything to Mocha, and it seems to work. Perhaps you may check the box for Mocha.
I'm using
mocha@^10.2.0.