Every Module object gets an Id property to identify it. This Id is usually the full path to the file, but in a Repl session it’s simply Repl>. Node allows many ways to require a file (for example, with a relative path or a Pre-Configured path) before we can load the content of a file into the memory we need to find the absolute location of that file. If you create a local Node_Modules

Resolving a local path

If you want to only resolve the module and not execute it, you can use the <code>require.resolve </code>function. This behaves exactly the same as the main <code>require </code>function, but does not load the file. It will still throw an error if the file does not exist and it will return the full path to the file when found.

require.resolve

Besides resolving modules from within the <code>node_modules </code>directories, we can also place the module anywhere we want and require it with either relative paths (<code>./ </code>and <code>../ </code>) or with absolute paths starting with <code>/ </code>.

Relative and absolute paths

Create a Lib/Util.Js file and add a Console.Log line there to identify it. Also, Console.Log the Module object itself. Do the same for an Index.Js file, which is what we’ll be executing with Node: NOTE how the main index Module (Id:' .') is now listed as the parent for the Lib/Util Module.

Parent-child relation between files

Module1 requires Module2, and Module2 requires Module1 while it wasn’t fully loaded. A property was reported because both B and C were exported after Module2 required and printed Module1. Node keeps this really simple: during the loading of a Module, it builds the exports object.

Circular module dependency

If a file extension was not specified, the first thing Node will try to resolve is A.Js file. If it can’t find A.Json file, it will try A.Json file and it will Parse The.Json file if found as a Json text file. After that, it will try to find a Binary.Node file. To remove ambiguity,

JSON and C/C++ addons

Node wraps the Module code in a function, which we can inspect using the wrapper property of the Module Module. Exports is defined as a reference to Module.Exports prior to that. Require and Module are both specific to the function to be executed, and __Filename /_Dirname variables will contain the wrapped Module’s absolute Filename and directory path. This wrapper function has 5 arguments: exports, require, Module, __Filename,

All code you write in Node will be wrapped in functions

We want to use this file in two ways: <ul><li>From the command line directly like this: </li></ul>

The require object

Learning React or Node? Checkout my books: <ul><li>Learn React.js by Building Games  </li><li>Node.js Beyond the Basics  </li></ul>

All modules will be cached

Create a Find-Me folder under Node_Modules and place an Index.Js file in there. The same require ('Find-Me') line will use that folder’s Index.Js file. We can control what file name to start with under the folder using the main property in Package.Json.

Requiring a folder

If you’ve noticed above, every time we’ve printed a Module object, it had an exports property which has been an empty object so far. So far, every time we printed a Module object, we saw a loaded attribute on that object with a value of false. The Module Module uses the loaded attribute to track which modules have been loaded (true value) and which modules are still being loaded (false value) we can, for example, see the Index.Js

exports, module.exports, and synchronous loading of modules

You can think of the require module as the command and the module module as the organizer of all required modules. The main object exported by the require module is a function (as used in the above…

Parent-child relation between files

Similar ideas to Parent-child relation between files

Resolving a local path

The idea is not the start-up

How To Create Rooms In a Memory Palace