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
Avoid creating new node processes by leveraging processAsync #57
Conversation
Do you think we can get rid of CJS completely and move all files to ESM ? |
|
I'd be in favor of that. It seems unrelated to this PR and best to do in a new one though |
I'm so sorry, but I disabled most of the tests with one of my older commits :( |
16e1460
to
7a86a71
Compare
at least you're not alone in making that exact mistake... sveltejs/kit#2069 (comment) |
PR LGTM! Feel free to merge when you're ready. Excited about this and also interested in moving to ESM in another PR if anyone is down for it. Happy to cut a release once we get that done. |
Cool. I guess the main thing is getting the tests re-enabled first. Is that something you're looking at @sebastianrothe ? |
Yes, I have them running, but I had to switch everything to ESM. Don't know if that's okay, or if we should keep CJS as well. |
I'd say go ahead and switch it to ESM |
remove old package
fix loading of config
esbuild is not needed anymore, since jest supports ESM now
Please have a look. |
I guess someone could run the code through Babel/Bundler and output a CJS version of it. |
Co-authored-by: Ben McCann <322311+benmccann@users.noreply.github.com>
LGTM |
Thanks for the work on this PR @benmccann and @sebastianrothe! Released in |
Oh crap. I was meant to major bump... |
BREAKING CHANGE: async transformers are only supported in Jest `>=27`.
Made a mess but all resolved and released in |
thanks!! |
Closes #25