DOCS: js: minor update for require

This commit is contained in:
Avi Halachmi (:avih) 2020-02-07 19:20:14 +02:00
parent 756960bf3c
commit c4570be3b8
1 changed files with 5 additions and 5 deletions

View File

@ -307,15 +307,15 @@ which ``require`` it. Otherwise it's considered a top-level id (CommonJS term).
Top-level id is evaluated as absolute filesystem path if possible, e.g. ``/x/y`` Top-level id is evaluated as absolute filesystem path if possible, e.g. ``/x/y``
or ``~/x``. Otherwise it's considered a global module id and searched according or ``~/x``. Otherwise it's considered a global module id and searched according
``mp.module_paths`` in normal array order, e.g. ``require("x")`` tries to to ``mp.module_paths`` in normal array order, e.g. ``require("x")`` tries to
load ``x.js`` at one of the array paths, and id ``foo/x`` tries to load ``x.js`` load ``x.js`` at one of the array paths, and id ``foo/x`` tries to load ``x.js``
inside dir ``foo`` at one of the paths. inside dir ``foo`` at one of the paths.
The ``mp.module_paths`` array is empty by default except for scripts which are The ``mp.module_paths`` array is empty by default except for scripts which are
loaded as a directory where it contains one item - ``<directory>/modules/``. loaded as a directory where it contains one item - ``<directory>/modules/`` .
``mp.module_paths`` may be updated from a script (preferably via custom init - The array may be updated from a script (or using custom init - see below) which
see below) which will affect future calls to ``require`` for global module id's will affect future calls to ``require`` for global module id's which are not
which are not already loaded/cached. already loaded/cached.
No ``global`` variable, but a module's ``this`` at its top lexical scope is the No ``global`` variable, but a module's ``this`` at its top lexical scope is the
global object - also in strict mode. If you have a module which needs ``global`` global object - also in strict mode. If you have a module which needs ``global``