-
Notifications
You must be signed in to change notification settings - Fork 48
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
Does not work with Yarn 2 Plug'n'Play (Berry) #295
Comments
Hey @AaronBuxbaum! Are you using Yarn 2s Plug n Play? |
Yup. Currently in loose mode, though hopefully eventually in strict mode |
Gotcha! Unless the changes are minimal, I don't think it's something we'll adopt. |
I wanted to add that we depend on OCLIF, which itself does not yet support PnP: oclif/config#171 Perhaps you may have some luck with Yarn's pnpify? |
this would be fine, but this is actually what I'm doing above. If I don't use pnpify, I get an error about being unable to find |
While we're waiting for oclif/config, I've done the following:
This is less than ideal because I have all of these dependencies of percy directly in my own package.json, but it's not a huge deal. Hopefully it can get resolved eventually. But it does work, for now at least! |
@AaronBuxbaum thanks for this workaround. I'd managed to get to step 4 on my own but didn't think to run Percy through pnpify 👍🏼 |
When trying to use
percy exec
with Yarn 2, the following is thrown:this is likely because you can't necessarily make the assumption that repos will be available, for example:
node_modules/@percy/cli-exec/dist/hooks/init
won't be correct because they're not under anode_modules
folder. However, even with this, you could theoretically install each plugin andyarn unplug
it.I think a biggest problem comes because it can't seem to find the
index.js
file when pointed at a folder:Any suggestions here?
The text was updated successfully, but these errors were encountered: