-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use import()
instead of require()
for commonjs/esmodule support
#162
Comments
Actually, we already worked on this, but it didn't make it into the In the meantime you could try out the version on branch |
Oooh, great! Not having es module support has been one of the initial problems for me trying to use this and jsfuzz w/ es module packages w/o bundling them fully |
We just merged a first step towards general ESM support. The remaining quirk is the instrumentation of ESM files, as intercepting loaded code requires custom Node.js loaders. We will continue to investigate this, though. In the meantime, could you please try out the current version on |
I'll close this as https://github.com/jasikpark/fuzz-prettier is using the typescript jest integration happily, import ESM packages as well 👍 |
I'm trying to get a fuzz harness set up for https://github.com/natemoo-re/ultrahtml but I'm running into a problem with the fact that the module is written as an esmodule instead of a commonjs module
It'd be great if
jazzer.js
supported es modules natively, ex:instead of
module.exports.fuzz = function() {}
or using TS to generate commonjshttps://github.com/jasikpark/fuzz-ultrahtml
The text was updated successfully, but these errors were encountered: