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
Jest encountered an unexpected token #11591
Comments
Same problem |
@KrisLau did you find any solution to this? |
If you believe there is a bug in Jest, it would be helpful if someone could provide either a repl.it demo or a repository on GitHub with a minimal reproduction. What's provided so far is unfortunately a little bit too diffuse/incomplete. See https://stackoverflow.com/help/minimal-reproducible-example for information on how to create good reproductions. Here's also some useful resources if you have questions or need help; |
@Fikir-2411 I actually ended up resolving the error but it was awhile back. I'm unsure which change actually fixed it but here is my jest config for reference
|
- jest import 버그 수정 - transformIgnorePatterns에 문장 추가 jestjs/jest#11591 (comment)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🐛 Bug Report
I keep getting the "Jest encountered an unexpected token" and I've tried a bunch of the fixes recommended online including:
adding
transformIgnorePatterns
to both of these:changing my
package.json
:AND
Creating a
.babelrc
file in my rootchanging the modules option of Babel's ENV preset from false to auto.
Actual error
> Prototype@0.0.1 test
> jest
To Reproduce
I'm not sure what caused it as I haven't created any tests in jest yet. I know it was working about a month ago but that's about it. The test that is failing is the sample that is created when creating a bare react native app so I doubt that's the problem.
My App.js
Expected behavior
For the jest test to run succesfully
Link to repl or repo (highly encouraged)
N/A
envinfo
The text was updated successfully, but these errors were encountered: