From cd4cf02398a6f7f19d439324cf67493b8d0fec10 Mon Sep 17 00:00:00 2001
From: Travis CI <travis@Traviss-Mac-5.local>
Date: Sat, 30 May 2015 20:28:13 +0000
Subject: [PATCH] update website

---
 docs/troubleshooting.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/troubleshooting.html b/docs/troubleshooting.html
index 64d54db014e..4b0aa79f6b7 100644
--- a/docs/troubleshooting.html
+++ b/docs/troubleshooting.html
@@ -7,7 +7,7 @@
 </span> <span class="token comment" spellcheck="true"> // iOS device are on the same Wi-Fi network.
 </span>  jsCodeLocation <span class="token operator">=</span> <span class="token punctuation">[</span>NSURL URLWithString<span class="token punctuation">:</span>@<span class="token string">&quot;http://localhost:9381/index.ios.bundle&quot;</span><span class="token punctuation">]</span><span class="token punctuation">;</span></div><h2><a class="anchor" name="watchman-took-too-long-to-load"></a>Watchman took too long to load <a class="hash-link" href="#watchman-took-too-long-to-load">#</a></h2><p>Permission settings prevent Watchman from loading. A recent update solves this, get a HEAD install of Watchman if you are experiencing this error.</p><div class="prism language-javascript">brew uninstall watchman
 brew install <span class="token operator">--</span>HEAD watchman</div><h2><a class="anchor" name="npm-locking-error"></a>NPM locking error <a class="hash-link" href="#npm-locking-error">#</a></h2><p>If in the <code>react-native init &lt;project&gt;</code> phase you saw npm fail with &quot;npm WARN locking Error: EACCES&quot; then try the following:</p><div class="prism language-javascript">sudo chown <span class="token operator">-</span>R $USER <span class="token operator">~</span><span class="token operator">/</span><span class="token punctuation">.</span>npm
-sudo chown <span class="token operator">-</span>R $USER <span class="token operator">/</span>usr<span class="token operator">/</span>local<span class="token operator">/</span>lib<span class="token operator">/</span>node_modules</div></div><div class="docs-prevnext"></div></div></section><footer class="wrap"><div class="right">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
+sudo chown <span class="token operator">-</span>R $USER <span class="token operator">/</span>usr<span class="token operator">/</span>local<span class="token operator">/</span>lib<span class="token operator">/</span>node_modules</div><h2><a class="anchor" name="debugging-in-chrome-hangs-and-or-does-not-work-well"></a>Debugging in Chrome hangs and/or does not work well <a class="hash-link" href="#debugging-in-chrome-hangs-and-or-does-not-work-well">#</a></h2><p>It is possible that one of your Chrome extensions is interacting in unexpected ways with the debugger. If you are having this issue, try disabling all of your extensions and re-enabling them one-by-one until you find the problematic extension.</p></div><div class="docs-prevnext"></div></div></section><footer class="wrap"><div class="right">© 2015 Facebook Inc.</div></footer></div><div id="fb-root"></div><script>
             (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
             (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
             m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)