4 ms·

I have run into problems in the past caused by forgetting to remove console.log() lines from my scripts. If the console wasn't open, then the scripts didn't wor

• notauser 16y ago
  You can solve(?) this by creating a dummy console.log object when one isn't already present, then throwing away all of the output.
• maxanger 16y ago
  if (window.console) console.log(...);
  • jackowayed 16y ago
    That really should be built in to console.log.
    • mitjak 16y ago
      I may not be entirely sober yet but I believe the problem at hand is what happens when window.console isn't defined at all.
    • ydant 16y ago
      It can be, but only if console.log is defined in your source code. It isn't when you use Firebug, so it won't be when you're not using Firebug.
• geocar 16y ago
  if(!console)console={log:function(){}}; You're welcome.
  • marcuswestin 16y ago
    This will throw if console is not defined. Try if (!window.console) Or if (typeof console == 'undefined') Or if !('console' in window)) N
    • geocar 16y ago
      Doesn't here. What are you using?
• toni 16y ago
  My solution to this issue was to write a console2.log helper function and call that instead of the original console.log: var console2 = { log: function(msg){ if(typeof console != 'undefined'){ console.log(msg); } } }
• devpopol 16y ago
  if(!window.console){window.console = {};} if(!(toString(window.console.log) === '[object Function]')) {window.console.log = function(){};} there, fixed..
  • jmtulloss 16y ago
    This won't work in node. That's not a huge deal, but it's pretty simple to come up with a cleaner solution that works in all environments.