Router without Vite

[inZaCz]

Hello, I have a question about using this library for Svelte 5 app without Vite. We freshly migrated our huge project from Svelte 3 to Svelte 5, but for now move from rollup to Vite is impossible.
Our legacy router used a lot of events and is kinda messy because of all the overtime hacks that we desperately need some modern router.

This one work great, but not for use because of import.meta.env. I have tried many hacks, but not successfully. (Our build is complicated)

The main problem looks like is here src/lib/helpers/runtime.ts where import.meta.env is undefined for us....

Would it be possible to fix this for non Vite users please? Simple if on import.meta.env...

Yes I know know there is also some way how to put there custom config but I did not figure it how to... because the initial export already call empty config() so this gives me no time to override the import.meta

Maybe another issue is for non Vite users is cicrular dependecny between runtime.ts and logging.ts, but t his we can ignore on our side....

Maybe I am overlooking something so please any kind of help will be bless for me.

Thanks very much..

Inza

[inZaCz]

Also I did not find a way to make the children routes works. It looks like the the router matching ignores them (we are using hash to navigate)

[mateothegreat]

Can ya share what you got that isn't working please?

For demo'ing child (nested) routes check out https://demo.router.svelte.spa/#/nested/level-1/level-2/level-3.

[mateothegreat]

Can you share a repro and I'll see what's up and get ya fixed up?

[inZaCz]

Hi thanks for reply.
When I wrote about children I did not mean the nestead router I was writing about route option children .
children?: Route[];
It looks like it is not fully implemented yet....

Also i have found that goto function is kinda of restrictive. Our project is kinda legacy and running in CEF where you have to have baseRoute set to Window.html and window.location.origin kinda ignores it. For now i am not using goto but later i would like to find some solution for it...

And for the non Vite users, i think it can simply be fixed when replace all of this
import.meta.env.SPA_ROUTER
with this
import.meta.env?.SPA_ROUTER
this shoud not affect any Vite users.

after the inicialization I can force there my own config,..

Sorry i can not share my repo...

[mateothegreat]

Closing, feel free to ping if this is still an issue <3

[inZaCz]

@mateothegreat
The Vite meta.env is issue no more, i have made some tweaks in our rollup, but still it would be better if i can omit the env hack,
But children are still a issue, i have also mentioned it here
#80