-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[Bug]: Module Import Stack Trace sometimes broken #13248
Comments
Could you put together a repository showing the regression? EDIT: Never mind, I'm blind - missed the link as it was in backtick 🙈 |
This only happens with SImilarly, just adding So I'm guessing something about how To test, apply this diff diff --git i/package.json w/package.json
index 6a6a596..f5615a2 100644
--- i/package.json
+++ w/package.json
@@ -11,5 +11,8 @@
"license": "ISC",
"dependencies": {
"jest": "^29.0.3"
+ },
+ "resolutions": {
+ "@babel/core": "7.18.13"
}
} (I wasn't able to get |
Thanks for the fast reply. I take a look at babel source code and issues tomorrow and see if they have a report for this. A fresh start seems to work, so it may be due to some internal babel caching I guess. |
Running Jest with |
I believe I've found the cause of the problem. The relatively recent In What's happening is as follows:
You could probably work around the problem with a change to how jest is setting/updating Hopefully this gives you and the babel team enough information to identify how/where to fix the problem. |
Ah, that makes sense, thanks for digging! Maybe open an issue in the Babel repo about it? I don't think what Jest does is unreasonable. |
Sure thing, will do it tomorrow (my time). Will link and share the issue here after I create it. |
Have raised the issue with the babel team (link above). |
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. |
Version
29.0.3
Steps to reproduce
git clone https://github.com/smcenlly/jest-stack-trace-issue
npm install
npm run test
Expected behavior
Described in steps to reproduce.
Actual behavior
Described in steps to reproduce.
Additional context
We have some automated integration tests as a part of our product (https://wallabjs.com) that test stack trace mapping for jest and identified this regression in the latest version of jest. I believe it is a result of @connectdotz commit: dbda13f.
Environment
and
The text was updated successfully, but these errors were encountered: