console: take care of console set undefined case

If global.console write undefined would come earlier than global.console read
then lazy read in get would happen, despite write was done.
This commit fix the problem.

Fixes: nodejs#11805

lib/internal/bootstrap_node.js

@@ -272,6 +272,7 @@
       configurable: true,
       enumerable: false,
       get: function() {
+        NativeModule.require('console').log( 'console get' );
         if (!console) {
           console = (originalConsole === undefined) ?
             NativeModule.require('console') :
@@ -286,7 +287,13 @@
         return console;
       },
       set: function(customConsole) {
-        console = customConsole;
+        NativeModule.require('console').log( 'console set' );
+        Object.defineProperty(global, 'console', {
+          configurable: true,
+          writable: true,
+          enumerable: false,
+          value: console
+        });
       }
     });
     setupInspectorCommandLineAPI();

test/parallel/test-console-assing-undefined.js

@@ -0,0 +1,21 @@
+'use strict';
+
+// Should be above require, because code in require read console
+// what we are trying to avoid
+// set should be earlier than get
+
+global.console = undefined;
+
+// Initially, the `console` variable is `undefined`, since console will be
+// lazily loaded in the getter.
+
+const common = require('../common');
+const assert = require('assert');
+
+// global.console's getter is called
+// Since the `console` cache variable is `undefined` and therefore false-y,
+// the getter still calls NativeModule.require() and returns the object
+// obtained from it, instead of returning `undefined` as expected.
+
+assert.strictEqual(global.console, undefined, 'first read');
+assert.strictEqual(global.console, undefined, 'second read');