nodejs · Tiriel · Nov 14, 2017 · Nov 16, 2017 · TimothyGu · Nov 14, 2017
diff --git a/doc/api/console.md b/doc/api/console.md
@@ -238,6 +238,15 @@ undefined
 >
 ```
 
+### console.debug(data[, ...args])
+<!-- YAML
+added: v8.0.0
+-->
+* `data` {any}
+* `...args` {any}
+
+The `console.debug()` function is an alias for [`console.log()`][].
+
 ### console.dir(obj[, options])
 <!-- YAML
 added: v0.1.101

diff --git a/lib/console.js b/lib/console.js
@@ -134,6 +134,9 @@ Console.prototype.log = function log(...args) {
 };
 
 
+Console.prototype.debug = Console.prototype.log;
+
+
 Console.prototype.info = Console.prototype.log;
 
 

diff --git a/test/parallel/test-console.js b/test/parallel/test-console.js
@@ -69,6 +69,13 @@ console.log('%s %s', 'foo', 'bar', 'hop');
 console.log({ slashes: '\\\\' });
 console.log(custom_inspect);
 
+// test console.debug() goes to stdout
+console.debug('foo');
+console.debug('foo', 'bar');
+console.debug('%s %s', 'foo', 'bar', 'hop');
+console.debug({ slashes: '\\\\' });
+console.debug(custom_inspect);
+
 // test console.info() goes to stdout
 console.info('foo');
 console.info('foo', 'bar');
@@ -154,6 +161,10 @@ for (const expected of expectedStrings) {
   assert.strictEqual(errStrings.shift(), `${expected}\n`);
 }
 
+for (const expected of expectedStrings) {
+  assert.strictEqual(strings.shift(), `${expected}\n`);
+}
+
 assert.strictEqual(strings.shift(),
                    "{ foo: 'bar', inspect: [Function: inspect] }\n");
 assert.strictEqual(strings.shift(),
Original file line number	Diff line number	Diff line change
Expand Up		@@ -134,6 +134,9 @@ Console.prototype.log = function log(...args) {
		};


		Console.prototype.debug = Console.prototype.log;
TimothyGu Nov 14, 2017 Copy link Copy Markdown Member Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Per MDN, Starting with Chromium 58 this method only appears in Chromium browser consoles when level "Verbose" is selected. Thus for consistency, I don't think we should show debug logs by default, per default. Instead we could perhaps only display debug logs when an environment variable is specified. @nodejs/collaborators thoughts? apapirovski, sgtoj, stigok, and danielbayley reacted with thumbs up emoji apapirovski Nov 15, 2017 Copy link Copy Markdown Contributor Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. I like having debug be conditional upon some flag. Having it just be an alias doesn't seem that appealing. Trott Nov 15, 2017 • edited Loading Copy link Copy Markdown Member Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Firefox and I believe every other major browser do not require a flag for `console.debug()` to display. I'm not sure we should follow Chrome's practice on this one. (I'm not sure we shouldn't either. I guess it kinda makes sense in Node.js for `debug()` to be conditional. So, maybe?) Tiriel Nov 15, 2017 Copy link Copy Markdown Contributor Author Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. I think that choosing t to follow Chrome on this feature would mean getting a bit too much opinionated, and I don't think we should. As you said, no other browser makes this choice. The choice to restrain visibility of the debug should be made by the users IMHO, and Node should only provide the method. addaleax Nov 15, 2017 Copy link Copy Markdown Member Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. I’m good with this. If they want to, anybody can override this method in their App, globally, and possibly depending on environment variables…


		Console.prototype.info = Console.prototype.log;


Expand Down