Use case for absolute URL

[oleole39]

Hello,

I am working on a package for a Vue 3 app which first sets a baseUrl which is then in particular used by vue-router.

For that purpose, I am looking for a way to script the baseUrl change without rebuilding the app. I can have this to mostly work using sed in the built app's directory. However having only the path to search for instead of the full URL makes it prone to unlegitimate replacements (e.g. if baseUrl was initially "/" or "/a/", etc.). I wouldn't encounter this issue if I could search for strings such as https://mydomain.tld/ or https://mydomain.tld/a/ instead.

So currently, if I initially build the app using a full URL, I understand that this is vite which transforms the URL https://mydomain.tld/mypath/ into just a path /mypath/, as mentioned in the doc:

Full URL, e.g. https://bar.com/foo/ (The origin part won't be used in development so the value is the same as /foo/)

when I understand from vue-router's doc that it does not support full URL as base parameter:

This allows hosting an SPA at a sub-folder of a domain like example.com/sub-folder by having a base of /sub-folder

Doing so, the app eventually mostly works but the URL rewrite is poor, which I guess is related to vue-router.

Would you think of a better way to change baseUrl after compilation?
I understand from this old answer of @posva (vuejs/vue-router#2927) that full URL input support was/is deemed useless so far (although I don't get whether it is by principle a minimalist standpoint or whether it would implies changing the whole code approach), but here is one use case (maybe a bit "edgy") where it would be useful.