Summary  
This chapter explains how to use explicit relative paths (starting with ./ or ../) in `require` statements to import code modules, ensuring Node.js resolves local files correctly, avoids conflicts with core modules, and resolves paths relative to the requiring file.

General domain of usage  
Node.js application development

When you use `require` with relative paths in Node.js, you tell Node.js exactly where to find your custom modules. Always start a relative path with `./` for the current directory or `../` to move up one directory. This makes your code clear and avoids accidental conflicts with built-in modules or installed packages.

**Folder structure.**
```
project/
│
├── app.js
├── utils.js
└── helpers/
    └── math.js
```

ZnVuY3Rpb24gbG9nTWVzc2FnZShtc2cpIHsKICBjb25zb2xlLmxvZygiTG9nOiIsIG1zZyk7Cn0KCm1vZHVsZS5leHBvcnRzID0gbG9nTWVzc2FnZTs=

Y29uc3QgbG9nTWVzc2FnZSA9IHJlcXVpcmUoJy4uL3V0aWxzJyk7CgpmdW5jdGlvbiBhZGQoYSwgYikgewogIGNvbnN0IHJlc3VsdCA9IGEgKyBiOwogIGxvZ01lc3NhZ2UoYFJlc3VsdDogJHtyZXN1bHR9YCk7CiAgcmV0dXJuIHJlc3VsdDsKfQoKbW9kdWxlLmV4cG9ydHMgPSBhZGQ7

Y29uc3QgYWRkID0gcmVxdWlyZSgnLi9oZWxwZXJzL21hdGgnKTsKCmFkZCgyLCAzKTsgLy8gTG9nOiBSZXN1bHQ6IDU=

You should avoid omitting the `./` or `../` when requiring your own files. If you write `require('utils')` instead of `require('./utils')`, Node.js will look for a core module or a package in `node_modules`, not your file. This can lead to errors that are hard to debug.

Keep your project structure organized and use clear, explicit relative paths. If your project grows, consider using absolute paths with tools like `path.join` or setting up module aliasing, but always be consistent and double-check your paths when moving files around. Remember, relative paths are resolved from the file where `require` is called, not from where you run your script.

Which `require` statement correctly loads a local file named `utils.js` located in the same directory as the current file, and avoids accidental conflicts with Node.js core modules or installed packages?

Master the modular structure that powers every Node.js project. Work with CommonJS and ES modules, explore Node's core utilities for file and system operations, and manage external dependencies through npm. Build a clear understanding of how modular code, system tools, and packages connect to create efficient, maintainable Node.js applications.

Understand how Node.js organizes code through its modular architecture. Explore how modules are loaded, shared, and managed using the CommonJS system, and apply exporting, importing, and path resolution techniques to structure scalable projects.

Move beyond CommonJS by adopting modern ES module syntax and combining it with Node's built-in capabilities. Work with the fs, path, and other core modules to manage files, directories, and system operations while maintaining clean, modular code.

Integrate system utilities and external dependencies to extend application functionality. Access system information through the os module and manage third-party libraries using npm for efficient package installation, updates, and dependency control.

Relative Paths in require

Awesome!

Relative Paths in require