Question 121540 in Redis Question posted in
The official documentation can be found here.

Redis – heroku nodered can't install modules

I’m trying to install the node-red-contrib-telegrambot and node-red-contrib-uuid modules in nodered in heroku and I get an error:

ERR! engine Not compatible with your version of node/npm: [email protected]
npm ERR! notsup Required: {"node":"0.10.x || 0.8.x"}

How to fix this error?

I did not install other modules here, these are the first ones.
Tried redis – same error
Although locally I had no problems with these modules.

BuildLogID:
Building on the Heroku-20 stack
Determining which buildpack to use for this app
Node.js app detected

Resolving node version 16.x
Downloading and installing node 16.14.2
Using default npm version: 8.5.0

Tags:

2

Answers


  1. 0

    The problem is with the follow which is used for tracking changes in CouchDB databases.

    Neither of those 2 modules you are trying to install appear to make use of this module in any of their dependencies this must be being driven by something else.

    If you examine the dependencies of the node-red-heroku installer it has nano@~5.11.0 which is what is pulling in the old version of follow with the outdated follow version.

    You need to raise this as an issue with against node-red-heroku on it’s git hub page: https://github.com/joeartsea/node-red-heroku

    In the meantime the error shouldn’t actually stop you installing and using the nodes you want.

    Login or Signup to reply.
  2. 0

    I dug into what @hardiilb was saying earlier in their answer, and digging further into my issue which I believe was very similar to yours:

    1. This issue was inhibiting my NR server’s ability to install nodes, let alone nodes that should have been installed by default like the email node (which was broken out of the core for some very strange reason)
    2. Attempting to update any of the nodes via palette manager was absolutely failing because of this same error babbling about engines or whatever.

    Fix [so far]

    I deleted the "nano": "~10.x", kvp and then I added all the npm modules that Node-RED was complaining about as dependencies in the package.json file like this:

    // fork of the joersarta/node-red repo
{
    "name"         : "node-red-heroku",
    "version"      : "0.1.0",
    "dependencies": {
        "when": "~3.x",
        "pg": "^8.3.0",
        "feedparser":"~0.19.2",
        "redis":"~0.10.1",
        "node-red": "~3.0.2",
        "node": "~18.11.0",
        "@sentry/node":"~7.16.0",
        "@sentry/tracing":"~7.16.0",
        "jsonschema":"~1.4.1"
    }
}

    Once I did that and deployed this branch I had made this change on, I was able to start using node-red and loading both custom nodes as well as custom modules with the function node as expected.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search