From 986c61323edb7b384a261f2a9f2c33ca12fcf470 Mon Sep 17 00:00:00 2001
From: Christopher Chedeau <vjeuxx@gmail.com>
Date: Wed, 9 Aug 2017 14:48:40 -0700
Subject: [PATCH] Explain how to clear the cache

This explanation by @thymikee worked like a charm! https://github.com/facebook/jest/issues/3705#issuecomment-312199902
---
 docs/en/CLI.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/en/CLI.md b/docs/en/CLI.md
index d07d44845daf..3dcc8482cbc7 100644
--- a/docs/en/CLI.md
+++ b/docs/en/CLI.md
@@ -84,6 +84,8 @@ Alias: `-b`. Exit the test suite immediately upon the first failing test suite.
 
 Whether to use the cache. Defaults to true. Disable the cache using `--no-cache`. *Note: the cache should only be disabled if you are experiencing caching related problems. On average, disabling the cache makes Jest at least two times slower.*
 
+If you want to inspect or clear the cache, use `--showConfig` and look at the `cacheDirectory` value.
+
 ### `--ci`
 
 When this option is provided, Jest will assume it is running in a CI environment. This changes the behavior when a new snapshot is encountered. Instead of the regular behavior of storing a new snapshot automatically, it will fail the test and require Jest to be run with `--updateSnapshot`.