Again: Thanks. I maybe should keep a better track of things.
It isn't I am trying to make things worse but as I have a horrible memory, I need to keep things "written down" - well you know what I mean - so I am not relying on my bad memory.
Some times I am working off line and can't just "google the answer".
I'm open to a better way. But in saying that, I would like to understand the mechanics of it as well. Not just "this is how you do it".
Ok, the node is/was used to monitor changes in the specified directory.
Not too complicated.
I am trying to search the library but I think the search is more for node names and not their functions.
(That's something I liked with the older library. I could load pages and pages of nodes and scroll through them looking for what I want. The new version doesn't allow that.)
Just if anyone knows of a node which does that, or could poke me in the right direction on how to make a node to do that.
The next thing to look at is the node-red log when it starts up as it will contain details of the actual error that is stopping the contrib-inotify node from loading. From the screenshot you can see the error says [object Object] - the fact it says that rather than an actual error message is a bug we fixed in more recent versions of Node-RED.