Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • Your answer seems best, but Mozilla's MDN page says console.error(..) is a non-standard feature and should not be used in production. What is your take on this? Do you have any suggestions for a novice programmer using console.error vs console.log? Commented Feb 27, 2015 at 21:27
  • This is interesting. We shouldn't use this then. Thanks for the info, Lucas. Commented Mar 13, 2015 at 15:18
  • 2
    MDN deems console.log(...) "non-standard" as well. In that regard, console.error is as stable as console.log. Commented May 7, 2015 at 14:29
  • 1
    @Lucas Who cares if it's standard? Who's going to use console logging for production? Commented May 2, 2017 at 19:05
  • 1
    Console.error works now in all major browsers. Even IE8. See developer.mozilla.org/en-US/docs/Web/API/Console/error Commented Sep 25, 2017 at 15:01