This is not something that we support and don’t currently have plans to. Strapi itself is headless, meaning it’s geared and built to ran on it’s own and not integrated into a frontend “channel” (as that would be a decoupled CMS). The Koa router can get very complex when it comes serving both a frontend and backend and our current implementation with the Admin panel is to handle this via a subfolder (IE /admin) with our landing page just being very simple and service static assets on the root (IE /index.html)
I would very strongly suggest you avoid joining the two within Strapi and handle this at a proxy level, we already have some guides for that here: Strapi’s documentation | Strapi Documentation
by trying to mix Vue and Strapi and serve them both from the same running process you are going to have the Vue Router and the Koa Router constantly fighting for control.