-
Notifications
You must be signed in to change notification settings - Fork 18
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
Regression in 2.1.2: a transform must export a process
or processAsync
function.
#74
Comments
Reproduction steps:
|
I will add some tests that mimic the usual usage to get this covered, finally. |
Can confirm that #75 fixes this issue for me. |
This does not appear to be released yet. When can we expect a 2.1.3 with this fix? Right now we're using jest 25 because we can't get 27 to work until this is out. |
For anyone else waiting for It has fixed all issues for me but YMMV. |
Sorry about the delay, released |
Thank you for the update! However, still having some issues: though not sure if I'm the only one, but still getting an error about the preprocess.js file:
|
I'm also getting that issue. When I look in the |
Yeah, sorry about that. Will be fixed, see #81 |
Just updated svelte-jester from 2.1.1 to 2.1.2 and now my tests won't run. "TypeError: Jest: a transform must export a
process
orprocessAsync
function." Reverting back to 2.1.1 makes the tests run again.I inserted some
console.log
calls into the loadTransformers() function from jest-transform and found that it ran three times. The first two times, it went through this block, but the third time it didn't:I inserted
console.log(transformer)
calls before and after that block, and got the following:First pass
Before:
After:
Second pass
Before:
After:
Third pass
Before:
After:
I don't know why on the third pass, the
transformer
value is thecreateTransformer
function instead of having acreateTrasnformer
property (i.e. it should be{ createTransformer: [Function: createTransformer] }
at that point). Being unfamiliar with the Jest code base, that's as far as I can get easily. But hopefully this will give you some idea of what part of the code might be causing this regression.The text was updated successfully, but these errors were encountered: