It doesn't seem like an arbitrary restriction to me though. The node.js ecosystem is a complete disaster if you're not tuned in to it, and if I want a fire and forget blog generated from static files then that's the complete opposite of node.js where you have to unfuck the imbred dependencies that form in the bloated, always changing ecosystem when someone decides to go CADT with their components.
I'm one of them, the most frustrating thing with working with modern JavaScript is definitely the ecosystem rather than the language. React Native is particularly an issue, the recommended react-native-community geolocation library just flat-out fails on many Android vendor's phones, and the replacement someone made for it still isn't exactly reliable (although to be fair, it only broke on OnePlus devices which were later patched so it could well have been an phone-level issue).
I get it, I shouldn't complain about the quality of open-source and freely offered software and the onus is on me to audit the libraries I put in my code, but blimey some people take an awful lot of liberty with the truth when they claim something is "production ready". I reckon a lot of people just build some rushed, poorly-written JavaScript libraries so they can pad out their CVs as an "open-source contributor" but the only thing they're actually contributing is a massive headache for muppets like me who foolishly use said code in their own projects.
