For me, a better method has been moving all of the logic of the component out to functions or classes in a package, and them importing those into the component. When you update the package’s logic, it also updates in all your GH-Files.
Very interesting solution from ladybug… I ll try get into.
Classes and packaging is great, but most of the time I have user interface issues e.g. input naming, type updates. Little minor things… but a bit tedious to update.
FWIW: It is possible to configure the component input/output nodes dynamically from the imported scripts as well. I don’t do this often, but if there are components where you know ahead of time that they will change a lot (or maybe where the options change based on the ‘type’ the user selected), it is sometimes worth setting them up this way.