Commit bbcb2a2
doc: clarify module loading behavior
The module loading system will not append node_modules to a
path already ending in node_modules. This used to be documented,
but it was lost.
Fixes: #3873
PR-URL: #3920
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>1 parent 0997178 commit bbcb2a2
1 file changed
Lines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -339,7 +339,8 @@ example, then `require('./some-library')` would attempt to load: | |||
| 339 | 339 | If the module identifier passed to `require()` is not a native module, | |
| 340 | 340 | and does not begin with `'/'`, `'../'`, or `'./'`, then Node.js starts at the | |
| 341 | 341 | parent directory of the current module, and adds `/node_modules`, and | |
| 342 | - attempts to load the module from that location. | ||
| 342 | + attempts to load the module from that location. Node will not append | ||
| 343 | + `node_modules` to a path already ending in `node_modules`. | ||
| 343 | 344 | ||
| 344 | 345 | If it is not found there, then it moves to the parent directory, and so | |
| 345 | 346 | on, until the root of the file system is reached. | |
0 commit comments