<p dir="auto">Uncaught Error: EACCES, open '/home/alex/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'</p>
<p dir="auto"><strong>Atom Version</strong>: 0.154.0<br>
<strong>System</strong>: linux 3.13.0-40-generic<br>
<strong>Thrown From</strong>: Atom Core</p>
<h3 dir="auto">Steps To Reproduce</h3>
<ol dir="auto">
<li>...</li>
<li>...</li>
</ol>
<h3 dir="auto">Stack Trace</h3>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="At fs.js:75

Error: EACCES, open '/home/alex/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'
  at Error (native)
"><pre class="notranslate"><code class="notranslate">At fs.js:75

Error: EACCES, open '/home/alex/.atom/compile-cache/cson/5af7724b023a6274b520f79f04fb798a67319ca7.json'
  at Error (native)

</code></pre></div>
<p dir="auto">I'm not sure if this is already possible in some way, or if it's desirable beyond a very specific use case I have run into.</p>
<p dir="auto">I would like to be able to write <code class="notranslate">require "react-atom-fork"</code> in a package and get access to the version of React used by Atom itself. This works around a <a href="https://github.com/facebook/react/issues/1939" data-hovercard-type="issue" data-hovercard-url="/facebook/react/issues/1939/hovercard">React bug</a> where having multiple copies of React on the same page leads to duplicate <code class="notranslate">reactid</code>s.</p>
<p dir="auto">If the bug is not worked around, React will give the following error when events fire:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Invariant Violation: ReactMount: Two valid but unequal nodes with the same `data-reactid`"><pre class="notranslate"><code class="notranslate">Invariant Violation: ReactMount: Two valid but unequal nodes with the same `data-reactid`
</code></pre></div>
<p dir="auto">This is admittedly a very niche use case, and obviously the right fix is inside React, but I thought I'd open an issue since I think anyone trying to use React in a package will run into this.</p>