My colleague just discovered that Chrome 58 (released April 19th) has silently muted all console.debug() output in their Chrome Dev Tools.

How? By making changes to the Console UI, from filtering based on type of console method to filtering based on levels. Introducing levels is not a bad thing in and of itself, but they also chose to – by default – NOT show all console output. Only level “Info” and below.

Depending on your project it might also be a big deal to no longer be able to filter by showing only one console method’s output, for example only console.log(). This is particularly troublesome if you’re working on a larger project with hundreds of different types of output mixed together.

Failing Tests

This means that if your app or project relies on console.debug() level output for testing, your tests might have been failing for over a month without you even noticing. With not as much as a popup warning or heads up from Google. By making it non-verbose by default, I believe Google has broken best practice here, and done a huge mistake.

Like this:

LikeLoading...

Related

Robert Axelsen

Robert Axelsen is a JavaScript Developer at Sipwise GmbH, and a passionate "life-long student" of all things code and dev.
When he is not busy with code or blogging, he tweets, runs a local Free Code Camp group in Vienna, spends time with his amazing wife and two daughters, and keeps up to date on all things tech. You can read more on his website.