Constant warning on node.js

[snajjar]

Hello,

Thank you for the hard work of bundling all of three.js into one package.
We use it daily on node.js as well as in the browser.

However, we constantly get the following warning on node.js.

It seems you are using this package in a non-browser environment. Some dependencies that depending on global window variable could not work properly.

Not that this is a high-severity problem, but we do ship node.js programs using three-full, and can not get rid of this warning, despite the fact that we got all our use cases tested. It's kind of breaking our front-end display.

I was thinking: could we move this warning in the actual examples that are relying on the window object instead of in the core three.js package? A quick grep shows that there's about 30 files using the window object (but it needs further investigations, some of theses have a "safe" try/catch usage of it).

[Itee]

Yes this warning is exactly here for that purpose, warn about Three class that depends on global window object and won't work properly in node.js environment.

But like we are in node.js env i will "map" this warning only on debug mode.
So to see it turn env DEBUG=* and if not set this won't warn anymore.