title: Technique for debugging Three.js
body: <p>I have a Three.js page that I'd like to update from r42 to r55. A fair amount of the API has changed in that time.</p>
  
  <p>Some of these changes were straightforward, but now I'm stuck on some gnarly details of the <code>JSONLoader</code>, for which the format has changed from JavaScript to JSON and possibly other changes are causing it to fail. An <code>undefined</code> value is tripping up the API somewhere internally, and I can't tell what the issue is because the top few layers of the stack are in minified code.</p>
  
  <p>What technique works best for getting the full source here? Are there <a href="http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/" rel="nofollow">source maps</a> available?</p>
  
  <p>I tried swapping the <code>three.min.js</code> file for <a href="https://github.com/mrdoob/three.js/blob/master/src/Three.js" rel="nofollow"><code>Three.js</code></a>, however the minified file contains many other files too. I don't like the idea of having to load all those files into my workspace and reference each of them just to debug a single issue for a minute.</p>
  
  <p>Is there a single file that contains the non-minified equivalent of <code>three.min.js</code>? Is there another approach that would work just as well?</p>
  
  <hr>
  
  <p><strong>EDIT</strong> So I'm cloning the three.js repo to get the source files, and will end up with a bunch of HTML like this:</p>
  
  <pre><code>&lt;script type="text/javascript" src="three.js/src/Three.js"&gt;&lt;/script&gt;
  &lt;script type="text/javascript" src="three.js/src/core/Object3D.js"&gt;&lt;/script&gt;
  &lt;script type="text/javascript" src="three.js/src/core/Geometry.js"&gt;&lt;/script&gt;
  ...
  </code></pre>
  
  <p>The repo is ~200MB and is taking an age to clone. There's no way to do partial clones with Git, apparently.</p>
  
  <p>There has to be an easier way!</p>