Re: Node and NPM don't work properly on some LPARS?

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

​Issues like this is why I've started saving off Node versions so I can
have multiple versions running on the same machine at the same time.
Here's my approach:

To save the currently installed Node.js to a tar file do the following:

$ cd /QOpenSys/QIBM/ProdData
$ tar -cvf /QOpenSys/node-0.10.??.tar Node/

Then when you want to load that version of Node you use

​$​ cd /QOpenSys/home/aaron/space1
$ tar -
​x
vf /QOpenSys/node-0.10.??.tar

​Then alter your PATH to have the new location at the beginning:

$ export PATH=/QOpenSys/home/aaron/space1/Node/bin:$PATH​


​Some of my syntax/paths might be off, but it is the general idea I wanted
to convey.  The tough part is you need to catch each version of Node.js
before installing the next version.


Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Oct 15, 2015 at 7:54 AM, Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx>
wrote:

> OK - well we have reported two main issues:
>
> 1)      A node child process should not just end unless it is a) killed or
> b) it runs process.exit()
> Our simple test code shows this failing in our duff LPARS, but OK on
> others with earlier versions of node
> 2)      When "npm install" runs it caches its packages in your local .npm
> folder. After that, it cannot access its own cache and every subsequent
> "npm install" fails with "uid must be an unsigned integer".  You have to
> run "npm cache clear" before every install to make it work!