Dynamic environment variables for SPA

[SvenBM]

I have a single page application written with sveltekit. In that app I want to use a dynamic environment variable , let's say PUBLIC_IS_TEST, I can consume it in svelte by import {env} from '$env/dynamic/public' and then use it : console.log(env.PUBLIC_IS_TEST)

That works fine when starting it via npm run dev. However, when I integrate the SPA in my backend (web-api with quarkus and kotlin) with quinoa, it works no longer. When there are some environment variables defined at build time, they get captured, but are fixed. I can't change them later for runtime.

Is there a way to solve that?

Update: for now I use Quarkus' environment variables and expose the ones, that are actually for the frontend via an endpoint. Not a real solution, but a workaround...

[melloware]

i am pretty sure that is just the way it works even outside Quinoa.

Typically most users have two env files one for Development and one for Production.

.env.development
.env.production

and if it uses Vite or most packagers it uses dev in dev mode and uses the production values in production build.

[SvenBM]

I started with the 2 files, but they are static. I need some switches for the already build package. Like the application properties of the quarkus app.

[melloware]

@SvenBM then you will need to write a REST Service that provides thse dynamic properties and have your Svelte app call first thing and get the configuration for the app. That is how its typically done for these types of things that are not BUILD TIME variables.

[SvenBM]

Well, thanks for the suggestion. I thought about that too. But I don't want to do a database roundtrip to decide if my app is in test mode or not.
Svelte does support dynamic environment variables like I wrote. Just not when deployed with quinoa. And I wanted to know, if it is possible somehow?

[melloware]

you would have to research. Quinoa in production mode is not involved Quarkus is just serving your static build JS files. Quinoa is only involved in Dev mode.

[melloware]

@SvenBM if you figure it out we should update the SVelte docs for other users who may have this question: https://docs.quarkiverse.io/quarkus-quinoa/dev/web-frameworks.html#svelte-kit-config