@AllanOricil - there was nothing wrong with your idea of how to implement nodes - GitHub - AllanOricil/node-red-vue-template: Write Node-RED nodes using Vue and Typescript . However the current core of Node-RED does not use either typescript nor Vue - so it would be a wrench to have to have those added as dependencies nd then have to track updates to those projects as well as all the (too many IMHO but :shrug: ) other dependencies we already have - we already bumped into that sort of thing with the original Dashboard and Angular 1 (which went EOL) . So yes - we're happy that your project exists - and happy for people to use it, There have also been several other folk suggesting that we rewrite the whole of Node-RED in typescript - and likewise they have been politely demurred. Again it is absolutely nothing personal.
Meanwhile back on track - yes I use Node-RED in production (albeit in a fairly non-traditional environment.) All developers have laptops where they can run Node-RED locally in order to do initial flow concepts, hopefully no power outages as on battery. They have access to non-live data and use injects and log playbacks to feed "data". Then we have a bunch of virtual vm environments where they can spin up instances to integrate as a team - and with more real sensor feeds (but not live) - which are also then used for integration with other environments, and demos etc (and are all backed up by IT) - and then finally there are live kit. So I would say 20% of time is spent solo on laptops - 60% integration and final 20% live. We regard the "annoyingly manual task" of moving flows as a positive thing to stop people deploying flows on a whim and a chance to inform co-workers that a change is about to happen etc... 
Ha, and there was me thinking that you'd retired! 
As I will be in just about 3 months now!
Mostly retired. Just do 2 days a week on what is effectively a zero hours contract.
