Installing npm packages with invalid name

I am trying to install bartbutenaers/node-red-contrib-ui-web-push from GitHub - bartbutenaers/node-red-contrib-ui-web-push: A Node-RED widget node to send web push notifications via the dashboard

There is an issue saying to install using npm install bartbutenaers/node-red-contrib-ui-web-push. This worked on a standalone nodered install.

In instance>settings>palette, if I enter install bartbutenaers/node-red-contrib-ui-web-push it says invalid name.

I exec’d into the instance docker container and ran the npm install command.
/usr/src/flowforge-nr-launcher/node_modules/node-red-contrib-ui-web-push exists but it isn’t displayed in the nodes pane in the editor

What is the correct way to go about installing this package? Thanks

It is node-red-contrib-web-push not bartbutenaers/node-red-contrib-ui-web-push :slight_smile:

Always check on the flows site or NPM for the correct name.


That install method is doing a direct from github install

Unfortunately there is no way to do this with FlowFuse, you can only install published versions from the Node-RED catalogue.

There is no exec node because this would pose a security risk in a cloud environment, but there are no useful tools to run with the exec node present in the container which backs a FlowFuse instance.

@Steve This is to install a pre-release fix version direct from GitHub head.

That’s listed as a dependency to the node i’m trying to install mate. I managed to install that okay

  • The node-red-contrib-web-push nodes can be used to send web push notifications to the device.
  • The node-red-contrib-ui-web-push node can be used to receive those web push notifications on the device.

My apologies, it has been a long 3 weeks :slight_smile:

It seems Bart has not published this to NPM.

The is an outstanding issue here: NPM not found · Issue #6 · bartbutenaers/node-red-contrib-ui-web-push · GitHub - you may wish to ask Bart to publish it.

1 Like

@Steve @Ben No problem, I can just use a standalone Node-RED install for now.
Will there be a way to install none Node-RED catalogue packages down the line?

Thanks for both getting back to me

There is already a way to specify “none Node-RED catalogue packages” - by adding it into the dependencies section of your FF instance (in the instance → settings → dependencies) - HOWEVER - that method still requires the package to have been published to NPM.

The immediate issue is that the author has not added this package to NPM. Once it is published and added to the Node-RED catalogue, you will be able to install it from the node-red palette manager (as normal) or using the method I described above.

However, if you mean will we permit packages to be installed directly from GitHub? I suspect that will require a change to the container image (to include git) and a slight tweak to our package entry validation. Afaik, there is nothing on the roadmap for this. @Ben would you be able to provide insight on if this - is it something we will/could/might support?

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.