The documentation explains that certain core modules are included in the Node.js platform itself and are specified within the source code. The terminology can get a bit confusing when it comes to details. The term "global objects" (or standard built-in objects) should not be mistaken for the global object. In this context, 'global objects' pertain to objects in the global scope.
From my understanding, there is a global object that can be accessed by explicitly typing 'global', such as:
console.log(global)
This global object contains elements that are meant to be used across all files, like the console or process object. There are other elements that may seem global but are actually not, as all Node.js scripts are implicitly encapsulated in the following structure:
(function (exports, require, module, __filename, __dirname) {
// Userland code goes here
});
There are additional objects that serve as the foundation of the Javascript language itself, such as Object, Function, or Boolean.
One thing I find perplexing yet significant is the fact that some components provided by Node.js can be accessed without external libraries, but still require 'require' statement (like the 'events' or 'fs' module). It appears that having a global object accessible to all files should expose core elements for easy access.
While I understand my query may be subjective, I wonder if this discrepancy is simply an implementation nuance or if there's a conceptual aspect that eludes me and needs consideration in daily development practices.