The charitable take: many of the younger f/end devs don't really know that $FRAMEWORK gets turned into Javascript. I've worked with one dev in the past 5 months who did not realise that Javascript is the underlying target of "compiling" their react project.
The uncharitable take: This was vibe-coded from a set of specs.
Like, I get it, it's no different than starting with a high level language like JavaScript itself, but just wow. I remember when we didn't have these frameworks at all, when they were just about adding the missing stuff to js or making things a little easier for people in that world. Didn't realise we had moved on so far.
I'm not being critical btw, from the down votes I guess it came across that I was being down on OP but I'm genuinely just so surprised.
While yea it is nice to directly deliver to HTML (I've done it many times), reality is most UI is in other framework languages. Plus I think a strong use-case is making output / browsing inside UI AI interfaces, which are also likely in a framework.
You provided enough for others who really care to add a direct-to-HTML plugin/fork if they so choose. Many of us want to use frameworks.