Misteriously when using the latest version of the lib on the project I'm working on I'm getting this error:
> Uncaught TypeError: Object [object Object] has no method 'set'
This is caused when THREE.UniformsLib.common.diffuse initialises a THREE.Color (THREE.Color.set() seems to be undefined then).
For some reason this only happens when I load Box2D before three.js. If I load it after is all good. But this fixes the problem too.
/ping @bhouston

fix three missed conversions to closures.  switch to extending math prototypes rather than replacing them.  This is to ensure that types created in closures within a type's prototype definition get their prototype updated with the full definition.

Removed Vector* add() to addVectors() and addSelf() to add(). Same with sub, cross, min, max, lerp... Renamed Matrix* and Quaternion multiply() to multiplyMatrices(), multiplyQuaternions() and multiplySelf() to multiply(). See #2860.
Good thing we have a ton of examples to make sure nothing is broken. The unit tests also helped. However, I suspect I've left something unchanged.

Renamed .multiplyMatrix* to .applyMatrix* and .multiplyQuaternion to .applyQuaternion as suggested by @WestLangley in #2860.

Makes the code so much nicer imho...

use switch statements in Vector2/3/4.getComponents()/setComponents() based on it being 5-10x faster than index-to-name based on benchmark_vector3components.html

inline Vector2/3/4/Quaternion.length()/lengthSq() and optimize Vector2/3/4.setLength() with unit test coverage.

fixed #2728, Moved geometry primitives out of src/core into src/math.  src/core is now exclusive scene primitives.

Vector2: setX, setY, Vector4: setX, setY, setZ, equals.  Unit tests for Vector2, Vector3 and Vector4.

Also trying to make a bit nicer UVs for ExtrudeGeometry / TextGeometry.

Some clean up on Vector* constructors.
Added UV::clone.

reworked Vector classes, no change in API, reordered methods, divide-by-zero prevention, removed use of .set() in methods for better performance

I don't remember when was the last time I used them. Current Web Developer Tools do this already for you.

Color::updateRGBA ⟶ Color::updateRGB

- getters/setters are no more in Vector3
  - object hierarchies thus don't use "isDirty"
  - this was completely killing performance for anything that was touching a lot of Vector3 like creation of meshes and dynamic buffers
  - even without this, performance of hierarchies went up (a lot)

- objects do not get passed renderer anymore
  - camera was almost also removed, but this is useful for LOD (though there may be some cleaner way to do this?)

- material ids are now unified, this makes "geometry.sortFacesByMaterial" faster (thus scene init / GUI blocking is shorter)

- all WebGL examples should work now (render-to-texture has weird lights and in some camera control feels different)

- CanvasRender still broken, despite many efforts :(
   - currently only points and lines work, faces don't show up. I think this may need assistance from mrdoob.