...
Profound Installer uses NPM and Node.js to install Profound.js and Profound API from the NPM online registry. Node.js and NPM must be installed separately on the target system before you can use Profound Installer to install products.
See the documentation for Profound.js and Profound API to determine what versions of
Node.js /NPM are compatible with the product versions you want to install. You should always use the most up-to-date compatible version of Node.js/NPM. For example, at the time of this writing the current version of Profound.js was version 6. Profound.js version 6 supports Node 14, 16, and 18. This means that you should generally use Node 18 with Profound.js 6, unless your application requires an older version for some reason.Node.js and NPM are bundled together. There are many options for installing, see here.
- For Windows and Linux, it’s recommended to use a tool like nvs (Node Version Switcher) as this allows you to install multiple versions of Node/NPM side-by-side and switch between them as needed.
- For IBM i, the only option is to install from the online repositories provided by IBM, via the yum package manager. See here for detailed information on how to set up yum on IBM i.
For IBM i, Profound Installer is able to detect/discover available Node.js/NPM versions on the system and will allow you to select from compatible versions. For other platforms, Profound Installer uses the PATH environment variable to locate Node.js and NPM.
See the documentation for Profound.js and Profound API to determine what versions of Node.js/NPM are compatible with the product versions you want to install. You should always use the most up-to-date compatible version of Node.js/NPM. For example, at the time of this writing the current version of Profound.js was version 6. Profound.js version 6 supports Node 14, 16, and 18. This means that you should generally use Node 18 with Profound.js 6, unless your application requires an older version for some reason.
SSH Server (for remote installs only)
...