-
Notifications
You must be signed in to change notification settings - Fork 29
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] Does not work with pnpm #277
Comments
@mczapkowicz you are right, we did not test pnmp compatibility. That the issue you are facing should be relatively easy to work around: you can set |
Thanks for the answer @mdjastrzebski . Yes, I tried that already by running fallowing command: |
Is that the same error or different one? Pls paste exact error details. |
Yes, the error is exactly the same: |
I think we've confusing two things here. One is TEST_RUNNER_PATH which should have path to test runner, e.g. Jest
|
gives me:
|
|
I'm using macOS. Everything works fine with yarn and npm so I belive this is package manager specific. |
@mczapkowicz do you have some available time and would like to bring PNMP support to Reassure? 😀 The issue here seems to be specific to how PNPM works rather than the actual Reassure code. |
I will take a look at this. |
Same problem here using on macOS, seems related to pnpm indeed. |
For anyone that may benefit, i was able to make this work with Note that this exact solution may not work for everyone as it relies on relative path. Takeway here is that for test runner we rely on Will try to submit a PR so that hacking like this is not required |
It seems the issue has been resolved. I successfully installed and ran Reassure in pnpm + Vite + ts-jest and pnpm + CRA + Vite environments, and it worked perfectly 👌 Can someone involved confirm this? |
Describe the bug
When using pnpm as a package manager reassure binary cannot be found.
After running command pnpm reassure i get:
ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL not found: reassure
I noticed that reassure binary is missing in the node_modules/.bin folder.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: