Long story short:
Dev does not have time. Plus, they perceive that numerous, under the hood changes are eventually going to be required in order to make it even viable, medium term in order to work with NC’s new Vue.js changes that are non-backwards compatible. Which they are very and highly likely unable to do, or do not want to, do due to previous mentioned reason.
There are some breaking changes you might be able to fix via light hacking, but they do not guarantee full or future usability and they would have to be applied on every update. These can be found in their Github.
If you are an end usre who only wants for it to just work, it would be wiser to either stay in your working environment for as long as you can, and/or simply look for a different solution. Otherwise, you will be left waiting for a number of “what if’s” to line up.
I used it briefly for a while and could see this outcome was likely to be the case and dropped using it since I did not want to be having to apply changes every time I updated… Perhaps this might be your best end goal, too.