-
Notifications
You must be signed in to change notification settings - Fork 1.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
Support .ava
cacheDir for better compatibility with Yarn PnP
#3226
Comments
node_modules
for better compatibility with Yarn PnP
I was thinking about this the other day actually, and yes I agree that should be an option. Placing it under
However this does leave us with the following code: Lines 210 to 217 in 4dc385b
The way this could work is:
And then we'd have to document that as a caveat. What do you think? |
node_modules
for better compatibility with Yarn PnP.ava
cacheDir for better compatibility with Yarn PnP
Wow, sorry about the incredibly delayed response! I'm not a huge fan of polymorphic variables personally, so it seems cleaner to leave Would you be ok with that? |
@andrewzey that's fair. Maybe Thinking about the |
Hello,
We're using Yarn 3 with PnP in our mono-repo, and find that ava is creating unwanted
node_modules
directories in our workspace (withnode_modules/.cache/ava/failing-tests.json
) This is a result ofava/lib/cli.js
Line 256 in f047694
Sometimes the existence of
node_modules
confuses the pnp patched executables (eg.eslint
), so the mere existence ofnode_modules
can sometimes cause issues with things working reliable.It would be great if you supported some manner of specifying the cache directory or simply defaulted to
projectDir/.ava
and recommended adding.ava
to the.gitignore
.Thanks!
The text was updated successfully, but these errors were encountered: