You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
three.js exposes itself as a global, and when you'd use a more modular approach - for instance browserify - you'll quickly run into instanceof issues. For now, you're better off using three as a global and keep an eye on issues/pull requests dealing with modularization.
There are some libraries that assume THREE as a global variables such as the TrackBall controller.
I don't think that it is considered a good practice, and is problematic when using a more modular approach.
Is there some sort of guideline when writing components for THREE that states that THREE could be assumed global?
The text was updated successfully, but these errors were encountered: