| Info |
|---|
This setting is not used for locating Profound.js modules or files when running an application in a Workspace. In that case, only modules/files within the Workspace directory or a sub-directory can be used. Paths within a sub-directory must be specified as relative to the Workspace directory. If a program in a Workspace is called via PJSCALL or a proxy program, the IBM i library list is used to search for modules/files. |
| Note |
|---|
If using a subdirectory in a workspace, the workspace name and the nested directories/folders must be added to the pathlist in order for this to work. For example, add something like this to the pathlist: /workspaceName/folder1/folder2/... |
This property is used to provide the default pathlist. The pathlist is specified as an array of directories to search.
| Code Block | ||
|---|---|---|
| ||
pathlist: [ "dir1", "dir2", "dir3" ] |
The concept of a pathlist is similar to a library list in an IBM i job. Note, when Profound.js modules are called from Genie, the pathlist is inherited directly from the library list of a Genie job and the "pathlist" configuration setting is ignored.
If appendPJSPathlist option is enabled in config.js, the pathlist inherited from the library list is instead appended onto the pathlist configuration when using Genie, and modules will start searching from the config pathlist before going into the library list. This setting does not affect regular PJS pathlist usage.
The pathlist is used to search directory paths for Node.js modules within the modules directory of the Profound.js instance. It is used by APIs, such pjs.call(), when a module name is unqualified.
...