How to clean out local install of node-red

768 views
Skip to first unread message

Soheel Chughtai

unread,
Apr 30, 2018, 8:20:18 AM4/30/18
to Node-RED
I am trying to start on a clean install of node-red on my local machine, but am struggling. 

I think I need to start clean as a recent switch between locations and networks had stopped my old instance from being able to load the palette. 

I have run npm uninstall, both with and without the -g option. I have run npm unlinks. I have renamed my .node-red directory. I have started from a clean directory.

I have tried to install node-red both through git and npm, but with every thing I try, node-red starts, but the palette just spins, and doesn't load anything. 

I currently have 

Node   6.12.3
npm     3.10.10

node-red 0.18.4 installed via git, with the
npm install

and
npm run build

 running successfully.

The first start couldn't find the .node-red directory, the second did, but the palette loader continues to spin. What else do I need to remove / uninstall?


30 Apr 13:17:39 - [info] 


Welcome to Node-RED

===================


30 Apr 13:17:39 - [info] Node-RED version: v0.18.4-git

30 Apr 13:17:39 - [info] Node.js  version: v6.12.3

30 Apr 13:17:39 - [info] Darwin 17.3.0 x64 LE

30 Apr 13:17:39 - [info] Loading palette nodes

30 Apr 13:17:40 - [info] Dashboard version 2.1.0 started at /ui

30 Apr 13:17:41 - [warn] ------------------------------------------------------

30 Apr 13:17:41 - [warn] [node-red/rpi-gpio] Info : Ignoring Raspberry Pi specific node

30 Apr 13:17:41 - [warn] ------------------------------------------------------

30 Apr 13:17:41 - [info] Settings file  : /Users/soheelchughtai/.node-red/settings.js

30 Apr 13:17:41 - [info] User directory : /Users/soheelchughtai/.node-red

30 Apr 13:17:41 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable

30 Apr 13:17:41 - [info] Flows file     : /Users/soheelchughtai/.node-red/flows_Soheels-MBP.home.json

30 Apr 13:17:41 - [info] Creating new flow file

30 Apr 13:17:41 - [warn] 


---------------------------------------------------------------------

Your flow credentials file is encrypted using a system-generated key.


If the system-generated key is lost for any reason, your credentials

file will not be recoverable, you will have to delete it and re-enter

your credentials.


You should set your own key using the 'credentialSecret' option in

your settings file. Node-RED will then re-encrypt your credentials

file using your chosen key the next time you deploy a change.

---------------------------------------------------------------------


30 Apr 13:17:41 - [info] Starting flows

30 Apr 13:17:41 - [info] Started flows

30 Apr 13:17:41 - [info] Server now running at http://127.0.0.1:1880/




Soheel Chughtai

unread,
Apr 30, 2018, 8:44:24 AM4/30/18
to Node-RED
Moving to node 8 seemed to do the trick, which I guess means that a feature of 8, or of the very latest 6 or 4, is required. Don't know what or why.

Welcome to Node-RED

===================


30 Apr 13:40:51 - [info] Node-RED version: v0.18.4-git

30 Apr 13:40:51 - [info] Node.js  version: v8.11.1

30 Apr 13:40:51 - [info] Darwin 17.3.0 x64 LE

30 Apr 13:40:52 - [info] Loading palette nodes

Soheel Chughtai

unread,
Apr 30, 2018, 1:02:31 PM4/30/18
to Node-RED
So it turns out that it was a directory problem. I was trying to create a clean install, but it was still finding my old node_modules, it was in ../../node_modules/ but still found. When I created a directory which couldn't find the old modules it started to work.


On Monday, 30 April 2018 13:20:18 UTC+1, Soheel Chughtai wrote:
Reply all
Reply to author
Forward
0 new messages