Opening node-red

General
21

yes, it is the node which I have created.
I did not know how I can test it before publishing.
Can you tell me how can I resolve it?

22

You can remove the "node-red" keyword from the package.json file - that way you can still post it to npm but we won't pick it up. While testing you should first just install locally by going into your .node-red dir and then npm install {path-to-your-dev-directory}/ to install it - restart Node-RED and test it... then when working use npm pack in your dev directory to create a .tgz file which again you can then npm install {path to your tgz file name}.tgz - maybe on a different machine to test that... then finally npm publish it to npm.

23

Thank you for the information.

24

Now, I have removed the node called :"sample" which was the issue.
I when I run node-red, I receive this:

Welcome to Node-RED

29 Jan 12:56:05 - [info] Node-RED version: v1.2.7
29 Jan 12:56:05 - [info] Node.js version: v14.15.4
29 Jan 12:56:05 - [info] Windows_NT 10.0.19041 x64 LE
29 Jan 12:56:05 - [info] Loading palette nodes
29 Jan 12:56:06 - [info] Dashboard version 2.25.0 started at /ui
29 Jan 12:56:06 - [info] Settings file : C:\Users\Admin.node-red\settings.js
29 Jan 12:56:06 - [info] Context store : 'default' [module=memory]
29 Jan 12:56:06 - [info] User directory : \Users\Admin.node-red
29 Jan 12:56:06 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Jan 12:56:06 - [info] Flows file : \Users\Admin.node-red\flows_DESKTOP-GC83620.json
29 Jan 12:56:06 - [info] Server now running at http://127.0.0.1:1880/
29 Jan 12:56:06 - [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.

29 Jan 12:56:06 - [info] Waiting for missing types to be registered:
29 Jan 12:56:06 - [info] - modbus-client
29 Jan 12:56:06 - [info] - Blockly
29 Jan 12:56:06 - [info] - countdown
29 Jan 12:56:06 - [info] - toggle

I guess those
29 Jan 12:56:06 - [info] Waiting for missing types to be registered:
29 Jan 12:56:06 - [info] - modbus-client
29 Jan 12:56:06 - [info] - Blockly
29 Jan 12:56:06 - [info] - countdown
29 Jan 12:56:06 - [info] - toggle

are the node-red-contrib-... nodes which I have removed them by entering npm remove node-red-contrib-...

25

yes - and shouldn't be a problem if you aren't actually using them. if you stop and restart again the warnings should go away if they aren't used in your flow.

27

I have restarted it again, but still the same issue!

28

In that case you have removed some nodes that you are still using, so you will have to install them again.

29

I installed them, but still does not work:

222
2221745×1189 109 KB

30

You can also install on another device direct from GitHub which is what I do when testing updated nodes before they are ready for wider release.

Yes :slight_smile:

If you are trying to write your first node, I strongly recommend using a simple template. Node-RED has one, see the docs. I also have a somewhat more complex, annotated example on my GitHub.

31

The screenshot you have shared shows Node-RED has started and is running. What about it isn't working?

32

No, it is not working.

333
3331441×779 16.3 KB

33

Now, after 28 minut I received this error:

29 Jan 15:48:27 - [warn] Communication send error: Error: WebSocket is not open: readyState 3 (CLOSED)

34

If the editor is stuck on the 'Loading palette' stage, then no amount of waiting is going to fix it.

Is this with the custom node you are developing installed?

Open up the browser developer console and have a look for what errors are reported.

35

I don't think so, it is not related to the custom node.
Please see this photo which is browser developer console:

444
4442595×866 154 KB

36

could you please help me?
@knolleary

37

Why do you think this isn't related to your custom node?

38

I do not know! just guessing

39

Instead of guessing, why not remove your custom node and see if Node-RED will start up?

40

I have tried that by inserting remove npm node-red-contrib-...

C:\Users\Admin>npm remove node-red-contrib-netio
npm WARN saveError ENOENT: no such file or directory, open 'C:\Users\Admin\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\Admin\package.json'
npm WARN Admin No description
npm WARN Admin No repository field.
npm WARN Admin No README data
npm WARN Admin No license field.

audited 735 packages in 3.757s

6 packages are looking for funding

  • run npm fund for details*

found 9 vulnerabilities (6 moderate, 3 high)

  • run npm audit fix to fix them, or npm audit for details*
41

Packages are not installed in that folder. With a typical Windows Node-RED installation, your userDir is: %USERPROFILE%\.node-red and that is where your user installed packages should be. You can see that when Node-RED starts, it tells you where things are.

Also, do yourself a favour and create yourself a standard user to use for day-to-day work. Running as Admin on Windows is like running as root on Linux. If anything bad comes your way, it will have access to just about everything.