From 00da533f109a0f82cf2d9d8af26d0f39666bf0a4 Mon Sep 17 00:00:00 2001
From: James Newton-King <james@newtonking.com>
Date: Tue, 6 Mar 2018 10:41:51 +1300
Subject: [PATCH] NPM troubleshooting documentation (#1529)

---
 docs/GettingStarted.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md
index f3fefcf44b..dd0a0111a7 100644
--- a/docs/GettingStarted.md
+++ b/docs/GettingStarted.md
@@ -18,3 +18,5 @@ Below are some tips for troubleshooting common issues.
 ### Project Load Failures in Visual Studio 
 In order to property load several of the projects in the solution, it is necessary that `%USERPROFILE%\.dotnet\x64` be in your `PATH` variable. If you experience issues loading projects in Visual Studio, please ensure that your `PATH` is configured correctly.
 
+### NPM Errors
+Running `build.cmd` or `build.sh` immediately after installing NodeJS can cause an NPM error: `EPERM: operation not permitted, rename`. Executing the NPM command `npm cache clean` will fix this issue.