-
Notifications
You must be signed in to change notification settings - Fork 339
jest-haste-map 22.4.0 breaks in node-chakracore #477
Comments
It is probably related to this bit jestjs/jest@3a2854a#diff-9450b62547fd20fe4b1669dd088f14af. The error I get is
It's reading a haste cache file but the file is empty, |
Can you try with 22.4.2? Ref jestjs/jest#5642. Doesn't chakra node support Underlying change: jestjs/jest#5565 |
I actually worked backwards from 22.4.2. The first version to work again was 22.3.0. |
/cc @mjesun |
The |
Ah nevermind; the |
Sorry for the late reply, I just got an email about that (thanks, GitHub...). From what you say it looks like it's not a particular bug in Jest? What would work as well for you is if you don't provide |
The difficulty with that is we kind-of/kind-of-don't support everything in the v8.js file. The simplest thing from our side would be to remove v8.js, but then your |
I think it's not unreasonable for v8.js to just return an empty object if process.jsEngine != 'v8'. @addaleax thoughts? (and yes, we probably should get around to supporting serdes at some point, it's still on my backlog 😞) |
@MSLaguana I can wrap the V8 require in a |
I've just put out a PR to have the |
This should be fixed in nightlies now, triggering the fallback to |
The fix was also backported to our latest release build: https://github.com/nodejs/node-chakracore/releases/tag/node-chakracore-v8.10.0 |
Just a heads up. I have a unit test that checks
jest
+mock-require
and it started failing after with the `jest-haste-map 22.4.0 update (on Windows 10).\cc @SimenB
The text was updated successfully, but these errors were encountered: