[Solved] OSX: Problem installing node-red@0.20.0 beta

#1

(a good deed never goes unpunished)
macOS High Sierra 10.13.6

So this morning I decided to install NR 0.20.0 beta 5 (first time installing 0.20.0) to test a bug I reported back in December marked 'fixed'.

So I user sudo npm install -g --unsafe-perm node-red@next and all hell broke loose. The install fails:

Pauls-mini-3:.node-red Paul$ sudo npm install -g --unsafe-perm node-red@next
Password:
npm WARN tar EISDIR: illegal operation on a directory, open '/tmp/npm-95562-60ca229c/unpack-61325073/examples'
npm WARN tar EISDIR: illegal operation on a directory, open '/tmp/npm-95562-60ca229c/unpack-61325073/src'
npm WARN tar EISDIR: illegal operation on a directory, open '/tmp/npm-95562-60ca229c/unpack-61325073/test'
<...SNIP...>
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/multilang-sentiment-0bf75575/test/unit'
WARN tar EISDIR: illegal operation on a directory, open '/usr/local/lib/node_modules/.staging/multilang-sentiment-0bf75575/utils'
npm ERR! path /usr/local/lib/node_modules/node-red/node_modules/js-yaml/bin/js-yaml.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/local/lib/node_modules/node-red/node_modules/js-yaml/bin/js-yaml.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/Paul/.npm/_logs/2019-02-14T09_23_23_426Z-debug.log

When I go look at /tmp/npm-95562-60ca229c it is empty, so nothing has been unpacked into it. If I look at it's ownership I see it is owned by root/wheel

Pauls-mini-3:tmp Paul$ ls -al
total 0
drwxrwxrwt  10 root    wheel  320 Feb 14 05:34 .
drwxr-xr-x   6 root    wheel  192 Jun 17  2018 ..
-rw-rw-rw-@  1 Paul    wheel    0 Jan 30 14:37 .keystone_install_lock
drwx------   3 Paul    wheel   96 Jan 29 09:50 .vnc-501
drwx------   3 tug     wheel   96 Jan 30 14:18 com.apple.launchd.EZDEB8O8S4
drwx------   3 tug     wheel   96 Jan 30 14:18 com.apple.launchd.cALJ055QjC
drwx------   3 Paul    wheel   96 Jan 29 09:49 com.apple.launchd.dxkgsJ53tE
drwx------   3 Paul    wheel   96 Jan 29 09:49 com.apple.launchd.zbumuD4jFl
srwxrwxrwx   1 _mysql  wheel    0 Jan 29 10:10 mysql.sock
drwxr-xr-x   2 root    wheel   64 Feb 14 04:22 npm-95562-60ca229c

Any ideas??

0 Likes

#2

Well, after some google searching, I finally blew away all my node directories and reinstalled node.js (which brought me to v10.15.1) and I was able to reinstall node-red.

Well that was fun (not)

0 Likes

#3

Interesting. Did you (or someone in the Googleverse) get to the bottom of the problem? I installed the beta 5 with node.js v8.11.2, no issues.

0 Likes

#4

I forun several ideas in the Goolgeverse and went in and hand removed all the 'node' occurrences in various libraries. That allowed me to reinstall node.js and tehn installing NR worked.

It was probably because of something I have done to my machine since I originally installed NR many many moons ago and I have no idea what it could have been. Since it is now working, I won't be looking at it (till the next time I try to upgrade - grin)

0 Likes