hey guys!!! I have the big problem!! I cannot use my node red.
please help me T-T
help me. I am crying now. because my project will be send this day.
You are using a very old version of Node-RED. Any reason you have not updated to 2.2.2?
This can be caused by badly implemented nodes. Have you installed anything new recently?
How to update?
I installed node-red-contrib-notifyimage and I write function node
msg.imagefile = msg.filename
return msg.imagefile
Restarting in safe mode (check the node-red docs) should let you restart and let you remove the offending node. But as Nick says, you might want to update to the latest version before trying that to see if it fixes the issue.
Not in this instance. The error is being hit whilst loading the palette - Safe Mode won't help.
msg.imagefile = msg.filename
return msg.imagefile
I'm sure this is not the cause of the startup issue but this code looks wrong
Normally a function would return the entire msg object rather than just one element.
(Is element the right word? Property?)
In a function you return a msg, so you would code return msg not return msg.imagefile
hey there, got a few days ago the same error on stable 2.2.2 Version and it was definitively a custom node which was not build correctly. In my case it was my own node which i was debugging.
so maybe navigating to your data folder usually .node-red and uninstalling the node with npm could fix the Problem.
the foreach is beeing run on an undefined object.
maybe nodered could also do an additional check here? This would improve the stability.
This is one of the reasons I suggest to upgrade. This is an area that has been improved since the old release being used.
i think here is an additional check necessary.
Edit:
Sorry i got the wrong line.
it crashed on node.type.foreach because type was undefined.
i could try to reproduce this error again. i think it was related to a wrong name inside the package.json of the custom node in the nodered section.
I got a typescript setup with yarn mono repo.
this way i can develop nodes and debugging them live in the code. In the background a node-red instance is started an installs these nodes.
So the error is reproducable if you set a wrong path in the package.json of your custom node. in the node-red section.
EDIT: See error in gif. Right click open picture in new tab makes it fullscreen 
@H3llsing it's completely unrelated sorry for that. But is there a chance you can share your TS setup with the hot reload? Have been looking for this and couldn't find something that checks all my boxes and is fairly recent
@vdhpieter hey there, im currently not at home, but next week im able to share my node including this setup i will reply with pm
@H3llsing sorry to bother you again, would you be open to sharing the node? Thanks in advance!
@vdhpieter hey pieter sorry i was on vacation i just fixed some testing stuff and here you go.
It's not perfect yet but at least a good start.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
