That looks like moving toward two clients @schlaegerz? 
Since here:
I have been always updating .babelrc and vite.config.ts and tsconfig.json in their respective format, to be able to use universal path aliases.
In that issue linked though, meteor-vite stopped obeying packages.json for where to get the entry points, and even started inserted code ( treating server as if it was client ) which then made me lose that feeling like this cannot ever be changed, since clearly @jorgenvatle is doing his own builds, kind of “over the top of” Meteor and not yet at the point of production.
( I believe? Not sure anyone is using Vite to build production. I feel like there is a dark cave here still. )