Clever Geek Handbook

Technique for debugging Three.js

I have a Three.js page that I would like to update from r42 to r55. At that time, the number of APIs changed.

Some of these changes were simple, but now I am stuck in some gnarly details JSONLoader

for which the format changed from JavaScript to JSON and possibly other changes are causing it to crash. The value undefined

disables the API somewhere internally and I can't tell what the problem is because the top few layers of the stack are in minified code.

What's the best method to get the full source here? Are there any source maps ?

I tried to replace the file three.min.js

with Three.js

, however the thumbnail file contains many other files as well. I don't like the idea of ​​loading all these files into my workspace and linking to each one just to debug one problem for a minute.

Is there a single file containing an unlimited equivalent three.min.js

? Is there any other approach that would work just as well?

EDIT So, I clone the three.js repository to get the source files, and I end up with a bunch of HTML, like this:

<script type="text/javascript" src="three.js/src/Three.js"></script>
<script type="text/javascript" src="three.js/src/core/Object3D.js"></script>
<script type="text/javascript" src="three.js/src/core/Geometry.js"></script>
...

Repo ~ 200MB and cloning age. There is no way to make partial clones with Git, apparently.

There must be an easier way!

+3


source to share


2 answers


Actually, this is what I do when I want to debug my code. Change three .min.js and put in three.js. The minified version contains the same code.

Unlimited version of the file is under version control:



https://github.com/mrdoob/three.js/tree/master/build

+3


source


  • use unminified assemblies
  • review the debugged debug points already present in three.js file (i.e. console.log)
  • 'use strict' if not already
  • add more console.log / debugs


+2


source






More articles:


All Articles