Three.js: Disable debug messages?

I am not sure If it's possible to disable the log's, but it probably should be, since you would not want that in production builds. (Maybe minifiers take care of it - dont know)

As a workaround you can override the console.log function while loading your meshes, and then reset it, like:

var oldLogFunction = console.log;

console.log = function(){}; // noop

// ... load meshes

console.log = oldLogFunction; // reset console.log

// ... perform debugging

That's works well, just note that in this case it's console.info :)

I agree with what you say about to production thing. I told my partner on this project what was happening, and he was surprised there was no option to disable the log messages

+1 to this. I'm working on a command-line tool that outputs a PNG on stdout, and overwriting console.log isn't a problem, but it is a bit of a wart.

The specific message I have a problem with is this one. It seems like in this specific case adding an option like quiet to the constructor would suffice. But it'd obviously better to have something a bit more all-encompassing I guess...

@crabmusket personally I think that message should always be displayed. It's very useful for anyone else looking at your app to know just by looking at the console that is was built with three.js, and the version. Consider it a tiny bit of advertising you have to put up with for using this free library 😉

Regarding the original issue, I don't think that any console.info messages get displayed anymore anyway, so perhaps this issue can be closed? @mrdoob @Mugen87

See the discussion in https://github.com/mrdoob/three.js/pull/5835.

I'm not going to continue this discussion because I think consensus has been reached, but I will just say:

It's very useful for anyone else looking at your app to know just by looking at the console that is was built with three.js, and the version.

I use Vue, Moment, jQuery, Bootstrap, and none of them think it's necessary to log mandatory messages to the console.