If it's going to be rendered by and live in a web browser it will either be complicated or limited in some way (like low code/no code tools).
Dealing with interactivity in the browser is subtle, complex and full of edge cases. JavaScript is also a horrible, broken language that’s not really fit for purpose. We’ve collectively invested a lot of time and resources trying to improve the experience of working with it, but the point still stands.
So could be useful for small projects but I wouldn't pick a solution like this for projects I would want to grow larger
You can be a lot more productive if you avoid JS entirely.
You can disagree if you want but that doesn't change the fact that JS is a huge pain in the neck to get the job done with.
https://transcrypt.org https://yourlabs.io/oss/ryzom#javascript https://github.com/am230/py2js
We get so much satisfaction out of writing JS in Python, it's worth all the IDEs in the world for us!
I tried using it a little bit but the reality is if you need JS to make your app more interactable it's really worth it to just learn some JS. As soon as you need something complex the extra layer of abstraction just gets in the way and becomes more of a headache, and if you don't need anything complex then you don't need a fancy JS solution in the first place.
JS only becomes complex when you are trying to create an enterprise version of your app along with a build platform. You can always just sprinkle in <script> tags in your HTML for simple one liners without getting into the weeds.