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

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

For a start, run these commands so we can see where things are pointing:

% which node | xargs ls -all
-rwxrwxr-x    1 qsys     0          26327031 Aug  6 02:13
/QOpenSys/QIBM/ProdData/Node/bin/node
% which npm | xargs ls -all
lrwxrwxr-x    1 qsys     0                76 Aug  6 02:13
/QOpenSys/QIBM/ProdData/Node/bin/npm ->
../lib/node_modules/npm/bin/npm-cli.js

In the first Node.js delivered by IBM I needed to do the following.  I run
node_env.sh each time I do Node work in a new shell session.  I also do
stuff like this in a shell file for when I start Node.js servers in "batch"
(daemon).

% cat ~/node_env.sh
export
PATH=/QOpenSys/QIBM/ProdData/Node/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
export LIBPATH=/QOpenSys/QIBM/ProdData/Node/bin

If you want to affect your current process/shell-session make sure to use a
period when you invoke it:

% . node_env.sh


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


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

> In spinning back to node v0.10.35,  npm is now completely shafted:
>
> module.js:340
>      throw err;
>            ^
>  Error: Cannot find module 'npmlog'
>      at Function.Module._resolveFilename (module.js:338:15)
>      at Function.Module._load (module.js:280:25)
>      at Module.require (module.js:364:17)
>      at require (module.js:380:17)
>      at /QOpenSys/QIBM/ProdData/Node/bin/npm:19:11
>      at Object.<anonymous> (/QOpenSys/QIBM/ProdData/Node/bin/npm:87:3)
>      at Module._compile (module.js:456:26)
>      at Object.Module._extensions..js (module.js:474:10)
>      at Module.load (module.js:356:32)
>      at Function.Module._load (module.js:312:12)
>
> Any ideas?  Looks like we have shafted a symbolic link somewhere perhaps.