For context, this Reddit comment I posted a while back explains some more of the reasons from moving away from NW.js. I know these transitions can be disruptive, but in the long run it's necessary to improve things, and by now the new exporters should support pretty much everything NW.js used to, such as with the File System object for accessing files and folders on disk.
I'm actually glad we moved away from NW.js, because shortly after the move, this bug broke support for Steam. As the relevant feature is undocumented and unsupported, nobody is obliged to fix it, so it may well be broken permanently now. I always knew it was a risk relying on things like that because of the chance of exactly this scenario, and that was part of the motivation to move away from NW.js. Luckily we avoided that particular nightmare. Presumably if we had stuck with NW.js, that bug would be causing serious problems, and everyone would be demanding a fix or talking about other better technologies we ought to be using instead. Also moving to new technologies has enabled further improvements, such as better support for dual-GPU devices in the latest releases.
In these cases we have to choose between continuing to suffer the faults of the technologies we've already chosen, or switch to better technologies and do our best to smooth the transition between them. If we have to choose between short term gain with long term pain, or short term pain with long term gain, in the end it's always best to choose the latter.