-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
option to specify cache directory #684
Comments
@borisovg I believe you already should be able to configure the cache directory using Assuming this works for you, I'd happily take a pull request that documents it. |
@bcoe I've just tried that option and now the cache directory is not being created at all, but tests run without issue. Here's the command I that I am running:
Edit: Actually, it does get created as |
And really the cleanest solution would be to by default create those directories relative to the current working directory (as opposed to the In my case it would mean they would be created within somewhere within |
Or you could use the
for example. |
I confirm that the |
Has this been addressed by #968? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I am running
nyc
from within myROOT/tests/
directory (which has a separate privatepackage.json
file that pulls in all test related libraries and I use--cwd ../
option when running tests.After tests are finished there is
ROOT/node_modules/.cache/nyc
directory created (i.e. outside ofROOT/tests
) which is annoying for apps that don't depend on anything and also apps that commit dependency code to git for various annoying operational reasons.Please make the cache directory location configurable, similar to
--temp-directory
.The text was updated successfully, but these errors were encountered: