Yeah, I understand how Nodejs works. But what you’re describing is already done in most Nodejs standard stacks.
Meteor actually does exactly what you’re describing, for the most part. As far as defining your routes just once, that’s already how every Node app I write works, as does Meteor.
It’s the idea of rendering the page on the server first, specifically as described here. It’s redundant to create another service to handle this when that’s effectively what shadow DOM is for, and what node already does.
I’m not clear how this set of “fake” modules is different, from say a MEAN stack or Meteor.