Logging is still a very good tool, but you cannot just depend on using tools such as console.log() or console.error(). Even though they do the work for a short debugging run, if you plan to include logging more seriously and want to disable it in production, you'll have a lot of work chasing down every logging call—or monkey patching the console object so .log() or .error() won't do their thing, and that's even worse!

Back in the Adding logging with Winston section of Chapter 5, Testing and Debugging Your Server, we used Winston for logging (and also Morgan, but that was specific for HTTP logging, so it doesn't count) and that library had features that enabled us to easily start or stop logging. There's no version of Winston for browsers, but we can fall back to debug, an old standard (we referred to in the There's more... section at the end of the chapter we just mentioned) that happens to work on the web as well.