docs: add a debugging cache doc

gatsbyjs · sidharthachatterjee · Feb 19, 2019 · Oct 15, 2018 · Oct 15, 2018 · Oct 15, 2018
commit f24aa24ca6eb9ae0559ee1bb767e18c487a9d5af
diff --git a/docs/docs/debugging-cache-issues.md b/docs/docs/debugging-cache-issues.md
@@ -0,0  1,36 @@
 ---
 title: Debugging Cache Issues
 ---
 
 There can be certain scenarios in which the Gatsby caching mechanism appears to fail, which leads to issues like:
 
 - Content not appearing when it should
 - Changes to plugin source code not appearing to be invoked appropriately
 
 and more! If you've found yourself writing a script like:
 
 ```json:title=package.json
 {
   "scripts": {
     "clean": "rm -rf .cache"
   }
 }
 ```
 
 consider utilizing the `gatsby clean` command which will help to resolve caching issues for you.
 
 First - make sure the version of `gatsby` specified in your `package.json` dependencies is _at least_ `2.1.1`, and then make the following change to `package.json`:
 
 ```json:title=package.json
 {
   "scripts": {
     "clean": "gatsby clean"
   }
 }
 ```
 
 Now when you issues arise that seem to be related to caching, you can use `npm run clean` to wipe out the cache and start from a fresh slate.
 
 _Note: If you find yourself using this command regularly, consider helping us out and [responding to our Github Issue][github-issue] with clear reproduction steps._
 
 [github-issue]: https://github.com/gatsbyjs/gatsby/issues/11747
diff --git a/www/src/data/sidebars/doc-links.yaml b/www/src/data/sidebars/doc-links.yaml
@@ -195,6  195,8 @@
           link: /docs/debugging-replace-renderer-api/
         - title: Debugging the build process
           link: /docs/debugging-the-build-process/
         - title: Debugging Cache Issues
           link: /docs/debugging-cache-issues/
         - title: Trace Gatsby builds
           link: /docs/performance-tracing/
     - title: Adding website functionality