It's really great. Thanks for implementing that.
It was a split response...
But I see benefit myself.
It’s neither right or wrong - just something that Is now possible.
I don't use it myself yet, but wont have any issue in using it where needed
Thanks for the praise. It was heated/ much debated feature that I felt strongly about but got equal and opposite strong pushback. It was a ride for sure. What I hope gets accepted next is "function modules " and "MQTT Request Node "
Waiting for these (well function node) with baited breath
Glorious! Best thing I've seen for node red ever. We also use another low-code service "thingsboard" which also has js lib. Discussed it a year ago:
I know there are multiple backdoors into node red for creating reusable functionality. But I'd like a first-class javascript library instead. It would be much easier to view and edit a shared js code inside node red, than having to go backend and restart on each change. I'd like something similar to a subflow, but not as independant instances with separate context (or even context at all). I also don't like the function library for obvious reasons.
Any plans or possibilities for this?
I assume you are referring to this:
Anticipating the pushback: some folk will argue this detracts from Visual Flow based Programming - and to a degree, that's a valid point. But there's already a common pattern, often suggested, of storing functions in context to write once, use many times (DRY). This prototype is an attempt to formalise that existing practice while bringing it as close to expected IDE behaviour as possible (within the existing confines of the Node-RED editor).
Click me for bigger view
