How do I read environment variables from a SvelteKit website?
Hiya,
I can't find any resources on how to set up SvelteKit to read environment variables from cloudflare pages environment variables set in the cloudflare dashboard. If anyone knows how to do this, it would be greatly appreciated :-)
10 Replies
Sounds like you've already done half of the work. Once it's defined in the dashboard then use dynamic private for runtime. That's all there is to it.
https://svelte.dev/docs/kit/$env-dynamic-private
$env/dynamic/private • Docs • Svelte
$env/dynamic/private • Svelte documentation
heya, thanks for the help! it now builds successfully, but I don't believe my app can access my api key as the page relying on it won't work. everything works fine in a local server. is there something specific I need to do with cloudflare secrets?
reading the value of WorkersAPIKey at runtime with a console.log spits out null
nvm, tried switching the secret to a plaintext env variable just to test, and still nothing :(
oh
my god
environment variables only apply to prodðŸ˜
I was testing on a preview branch
Lol. Sounds about right. Just gotta add the variables to the preview env. So any updates to variables should be done both on preview and prod.
Hello, @Soly
I think you are developing sveltekit project
I am a full stack sveltekit developer.
May I DM to you?
@kooliebwoykg this does not work for workers deployments only for pages right?
Hey, @apolodoro ! Same thing applies. I've actually switched from pages to workers static assets and my codebase remained the same outside of the adapter and relying more on the wrangler.toml. Define your plaintext environment as vars in wrangler.toml/json and set secrets with the cli and you should be all sorted. Doing this ensures nothing is overwritten on deployments.
but do you have a .env or a .dev.vars?
.env in local. Whatever I define there, I also place a copy in wrangler.toml for production. Plaintext only. The secrets, I set with put cli command.
Nice! I will try
Actually I was testing just now and apparenlty if you set the variables in the variables and secret section of the git auto build section you dont even need to se variables through the cli or wrangler file. Just mirror your .env and you are set. Works also locally.
