Can't get my nodes to show up in the pallette

Developing Nodes
1

I've got my node building and unit testing. I've npm installed it and it's created a symlink to my project. When I go into Node-RED though, the node doesn't show up in my palette and when I go to manage my palette it doesn't show up under my installed packages.

Here's my package.json:

{
  "name": "node-red-contrib-fast-bandwidth",
  "version": "0.0.1",
  "description": "Test network bandwidth using Fast.com",
  "scripts": {
    "test": "mocha --timeout 40000"
  },
  "keywords": [
    "node-red",
    "bandwidth",
    "fast"
  ],
  "author": "jasoncarreira",
  "license": "MIT",
  "node-red": {
    "nodes": {
      "fast-bandwidth": "fast-bandwidth.js"
    }
  },
  "dependencies": {
    "chalk": "^2.4.2",
    "deep-equal": "^1.0.1",
    "delay": "^4.1.0",
    "log-update": "^2.3.0",
    "meow": "^5.0.0",
    "ora": "^3.1.0",
    "puppeteer": "^1.12.1",
    "zen-observable": "^0.8.13"
  },
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^4.22.0",
    "@typescript-eslint/parser": "^4.22.0",
    "chai": "^4.3.4",
    "eslint": "^7.24.0",
    "mocha": "^8.3.2",
    "node-red": "^1.3.2",
    "node-red-node-test-helper": "^0.2.7"
  }
}

Any help appreciated

2

I have to ask because you have not said. Have you restarted node-red since installing the node?

Edit: If it isn't that then stop node-red and start it again in a terminal and see if there are any errors in the log shown.

3

Yeah, I did. I'm actually running it in Docker with a volume mapped. I know it's loading the packages from the data volume because I've got another package installed that show up in the pallette. Here's my package.json from the data volume:

{
    "name": "node-red-project",
    "description": "A Node-RED Project",
    "version": "0.0.1",
    "private": true,
    "dependencies": {
        "node-red-contrib-fast-bandwidth": "file:../../node-red-contrib-fast-bandwidth",
        "node-red-node-ping": "^0.3.1"
    }
}
4

Now that I think about it, that's probably the problem because that file path will be running in the container and won't find my local path

5

Yup, that was it

6

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