/
Updating Profound.js 5 and Earlier Versions

Updating Profound.js 5 and Earlier Versions

Profound.js 5 and 6 are no longer supported. This page is retained for reference only and must not be used for a new installation or upgrade. For the current release, see Installation Process and Upgrade Process.

Overview

The update process is initiated from a shell command line. On IBM i, in a 5250 session, you can use CALL QP2TERM or the QSH command to start a shell. Alternatively, connect to your IBM i server via SSH, which provides a friendlier interface for working with Node.js on the command line. For more information on configuring SSH, see https://wiki.midrange.com/index.php/SSH.

Next, use the cd command to go to your Profound.js installation directory. The commands below are run from there.

Checking the Current Version

To display the current Profound.js version:

npm list profoundjs

To see which versions of Profound.js are available, visit https://www.npmjs.com/package/profoundjs.

Updating Profound.js

To update to the latest 5.x.x release, use the latest-5 npm tag:

npm install profoundjs@latest-5 --save

Then follow the instructions on Installing Profound.js 5 and Earlier Versions.

Updating Profound UI Static Files

Older releases used a separate script to refresh the Profound UI static files used by the Profound.js installation:

node updatepui

The updatepui.js script is obsolete. On current releases it does nothing except print the message β€œThe updatepui.js script is now obsolete and can be removed.” Profound UI static files are handled by the installation process itself.

Updating to a New Major Release

To move off Profound.js 5 onto a current release, see Migrating to a New Major Release and Installation Process.