From bbcb2a2e6537faa982aaedc79588230d0e3b1c33 Mon Sep 17 00:00:00 2001 From: cjihrig Date: Thu, 19 Nov 2015 12:05:47 -0500 Subject: [PATCH] doc: clarify module loading behavior MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: https://github.com/nodejs/node/issues/3873 PR-URL: https://github.com/nodejs/node/pull/3920 Reviewed-By: James M Snell Reviewed-By: Michaël Zasso --- doc/api/modules.markdown | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/api/modules.markdown b/doc/api/modules.markdown index e9db1e4b225cbc..5c1d7671e4f701 100644 --- a/doc/api/modules.markdown +++ b/doc/api/modules.markdown @@ -339,7 +339,8 @@ example, then `require('./some-library')` would attempt to load: If the module identifier passed to `require()` is not a native module, and does not begin with `'/'`, `'../'`, or `'./'`, then Node.js starts at the parent directory of the current module, and adds `/node_modules`, and -attempts to load the module from that location. +attempts to load the module from that location. Node will not append +`node_modules` to a path already ending in `node_modules`. If it is not found there, then it moves to the parent directory, and so on, until the root of the file system is reached.