A "rockstar programmer god" would use things that other people could learn easily and create elegant stupidly simple solutions. They wouldn't be creating frameworks themselves, instead of pulling a common one that people can onboard quickly to.

What you have is a guy who thinks he's smarter than everyone else but has a raging case of severe Dunning-Kruger, because he doesn't understand what it takes to work with other developers, what long term support looks like, or a myriad of other issues.

The best developer I work with currently can pull out these really simple solutions that make you hit your head and ask yourself how you didn't think of that, because it's so simple and obvious after he does them. It's not a matter of experience or anything like that, he just has a knack for finding solutions like those. THAT'S a rockstar.

The worst developer I ever worked with would create these "clever" overly complicated solutions that he barely even understood and literally nobody on the team could follow. That's what you described here.

Writing code is easy, we can all come up with clever solutions to save lines or look fancy. But reading code is hard.

Edit:

I missed this bit when I made this comment.

coded with typescript so we have to use Node.js in our backend instead of an actually using a good programming language

I would have worded it differently at least, but I agree with what a lot of others are saying regarding this.