Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unrecognized option "clearCache" from `jest --clearCache`
See original GitHub issuerunning jest --clearCache throws error Unrecognized option "clearCache". I am running v22.1.1
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (1 by maintainers)
Top Results From Across the Web
How can I clear the Jest cache? - Stack Overflow
As of Jest 22.0.0+, you can use the --clearCache option: Deletes the Jest cache directory and then exits without running tests.
Read more >Jest CLI Options
The jest command line runner has a number of useful options. You can run jest --help ... If you need to clear the...
Read more >Unrecognized option "clearCache" from `jest - Bountysource
running jest --clearCache throws error Unrecognized option "clearCache". I am running v22.1.1. See More. View in GitHub. SOLVE ISSUE.
Read more >How to Clear Jest Cache? - Designcise
To clear Jest's cache, you can do either of the following: Use the Jest --clearCache CLI Option;; Locate and Remove the Cache Directory....
Read more >API Reference | Vitest
In Jest, TestFunction can also be of type (done: DoneCallback) => void . ... export interface Options { /** * time needed for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We fixed our CI problem today. Inside our docker container, we got a node_modules folder in the root dictionary. Then somehow npm did pick the jest-cli from this parent node_modules folder instead of choosing the locally installed version for the project.
I think it is related by the fact, that the root folder did have a jest-cli package directly specified and the project had it only included by the jest package.
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. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.