Skip to content

Commit 9eea190

Browse files
committed
Fix NU_LIB_PATH -> NU_LIB_DIRS
`$env.NU_LIB_PATH` does not exist In the block that follows the correct name is being used.
1 parent bf790aa commit 9eea190

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/modules/using_modules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ The path to the module can be:
6969
Note that the module name (its directory) can end in a `/` (or `\` on Windows), but as with most commands that take a paths (e.g., `cd`), this is completely optional.
7070
:::
7171

72-
::: important Important! Importing modules from `$env.NU_LIB_PATH`
72+
::: important Important! Importing modules from `$env.NU_LIB_DIRS`
7373
When importing a module via a relative path, Nushell first searches from the current directory. If a matching module is not found at that location, Nushell then searches each directory in the `$env.NU_LIB_DIRS` list.
7474

7575
This allows you to install modules to a location that is easily accessible via a relative path regardless of the current directory.

0 commit comments

Comments
 (0)