Test Framework / Build Tool Support
guybedford opened this issue · comments
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.
Tools to Update
- Ava test framework:
- Blocker:
import.meta.urlis not supported in CJS
- Blocker:
- Mocha:
- Check if this works now that Mocha supports native modules
- Jest:
- Depends on Modules support: jestjs/jest#9430
- Update jsdom-worker
- RollupJS: Need to determine plugin combination for build support
- Ensure this works with rollup-plugin-off-main-thread
- Webpack: webpack/webpack#6719
- Fix in worker-plugin
- Fix in worker-loader
- Parcel:
- 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).
Here's a quick Babel hack that should make it work in Webpack.
Here's a quick Babel hack that should make it work in Webpack.
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?
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.