-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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 fails with: "Could not locate the bindings file" #1694
Comments
Thanks for reporting. This does seem like a bug! |
Awesome! Do you want me to create a repo to for reproducing the problem, or it's clear for you? |
A repo would be helpful, yes! Sorry for the bug. On Wed, Sep 14, 2016 at 11:21 PM -0700, "Eli Yukelzon" <notifications@github.51.almailto:notifications@github.com> wrote: Awesome! Do you want me to create a repo to for reproducing the problem, or it's clear for you? You are receiving this because you were assigned. |
Welp. It's always useful to create a reproducing repo. This way - you find out, that you are a dumb ass :) Apparently, I forgot that I had a preprocessor for Typescript, (ts-jest) and it was the one causing the problems. Jest is not at fault here. Yey! Closing the issue - no bug here. |
I've opened the bug in ts-jest kulshekhar/ts-jest#2 |
Just a note for posterity - this error was caused by the
|
@cpojer , with help of @kulshekhar we came to the conclusion that it is, in fact a problem with Jest. To check:
This repo doesn't use any preprocessors, it's just jest and javascript. Thanks in advance! |
@cpojer @reflog If you use |
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. |
Hi.
I have some code that depends on node-etcd, which in turn depends on deasync.
The code runs fine, under node 6.5 and 6.2.
I've added a simple test for that code using jest, and when executed, jest fails with the following:
Indeed, the files that are mentioned in the error are not present, but, to reiterate - when running the same test file without jest (just the actual test code) - it runs fine.
I guess something in the way jest initialises node environment confuses the bindings library.
If any additional details are need - I'm happy to provide.
Thanks in advance!
The text was updated successfully, but these errors were encountered: