13 Replies
Okay, in
vite.config.js
: Was just doing those on my own :p
The console should then have an entry
[vite] connected.
Somewhere at the top, a little below the Foundry logoIt's there, yeah.
Or at least a
[vite] connecting...
almost at the top of the log.
Looks like the template reloading suffers when a routePrefix is added thoughIf it fails to detect the prefix, then yeah, it wouldn't find things correctly.
Since it relies on
base
, which should not include the routePrefix within Foundry.
Welp, that I can work with though.The page launched by the serve command in browser also lacks the prefix, so it kinda just splats on 404 or similar.
The whole setup is absolutely not built with a routePrefix in mind 😄
Not that I ever use that, since it launches firefox for me, which is there just to not mess my tabs in the browser I actually use.
This will require some tinkering, but I think adding an option to
foundryconfig.json
and then handling base
and its dependants accordingly should be quite possible.While at it, could you add option to not open it in a browser?
Yep, might as well
I added
routePrefix
handling to the lang-reload
branch as that one already included some tooling changes. It should now be possible to have a foundryconfig.json
file like and get a working Vite development server including template hot reloading.
openBrowser
is a boolean
option, but I set the default to false
so you should not need to manually set it.