Palette editor disabled : npm command not found

4,350 views
Skip to first unread message

PM

unread,
Oct 18, 2016, 3:02:43 PM10/18/16
to Node-RED
Finally crawled to deploy Node-Red on Cloudno.de

But for any reason, I don't get the Manage palette menu, Node-RED on server says:

Welcome to Node-RED
===================

18 Oct 18:36:18 - [info] Node-RED version: v0.15.1
18 Oct 18:36:18 - [info] Node.js  version: v4.2.2
18 Oct 18:36:18 - [info] Linux 3.19.0-31-generic x64 LE
18 Oct 18:36:18 - [info] Palette editor disabled : npm command not found
18 Oct 18:36:18 - [info] Loading palette nodes
18 Oct 18:36:19 - [warn] ------------------------------------------------------
18 Oct 18:36:19 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
18 Oct 18:36:19 - [warn] ------------------------------------------------------
18 Oct 18:36:19 - [info] User directory : .nodered
...

Ok, Palette could be replaced, I tried to add mongodb:
npm install node-red-node-mongodb (locally, got a fsevents warning), then pushed on server.
but there's no mongo in the palette after ctrl+F5 and no Manage Palette in the menu.

Any idea how I can add modules to the server version?

Dave C-J

unread,
Oct 18, 2016, 4:07:33 PM10/18/16
to node...@googlegroups.com
we try to detect if npm is available - and if not then we don't enable the palette manager (as we need npm to install the nodes...) - so no - you won't be able to install nodes either... unless you install npm... which should then enable the palette manager  :-)

Nicholas O'Leary

unread,
Oct 18, 2016, 4:11:54 PM10/18/16
to Node-RED Mailing List
Hi,

I'm not familiar with cloudno.de so I don't know what the right way to add npm dependencies is. For that sort of environment, where npm isn't available, you'd include a package.json file that lists the dependencies and the platform will install them for you.... but I can't see anything in their docs about how to do that in practise.

Nick



On 18 October 2016 at 21:07, Dave C-J <dce...@gmail.com> wrote:
we try to detect if npm is available - and if not then we don't enable the palette manager (as we need npm to install the nodes...) - so no - you won't be able to install nodes either... unless you install npm... which should then enable the palette manager  :-)

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwKbRUV59tq3doJo8z1%3DdibjsxspZnWpj6CpvtcBnmR20Q%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

PM

unread,
Oct 19, 2016, 2:28:47 AM10/19/16
to Node-RED
Thanks!
I didn't expect such a quick reply, you're great!

Actually npm is present (old 2.15.0 version), of course I  can't upgrade it. Could it work with this version? Could it be forced?

I also tried to force with package.json (npm ... -- save to get "node-red-node-mongodb": "0.0.7",) then grunt build (took the 0.15.1-git version just to learn embedding for future express middleware)  before pushing.
I'm surprised to see that the result on server is not 0.15.1-git but 0.15.1 (not git).

Could it be fsevents warning at npm install?
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsev...@1.0.14

I triied bluemix, I can't say I had the best experience and wonder how I could push an embeded version with Express Passport to manage users. Or did I miss something?

PM

unread,
Oct 19, 2016, 2:31:08 AM10/19/16
to Node-RED
Or could we npm install npm (as local package) and force to use this one instead of the global one?

Dave C-J

unread,
Oct 19, 2016, 5:30:05 AM10/19/16
to node...@googlegroups.com
npm 2.x should be good enough... 
the error message is just a warn - so again - should be OK as long as there are no errors further down.]

On start we simply call  npm -v   and if there is an error we report that in the console and don't load the palette manager...   maybe the user that node-red is running as doesn't have permission ?

Manzano

unread,
Oct 19, 2016, 5:34:09 AM10/19/16
to node...@googlegroups.com
Hmm, it makes sense.
I'll try to grab someone on cloudno.de slack


--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/MS__CkL-OOk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
Reply all
Reply to author
Forward
0 new messages