Support `useEnvVars()` in Qwik

Is your feature request related to a problem?

It would be nice if environment variables could be supported in Qwik. Something similar to Next.js

Describe the solution you’d like

Pseudocode of what I have in mind.

function useEnvVars(): Record<string, string> {
  return useStore(process.env):
}

NOTE:

• The above code needs to be more complicated as multiple calls to useEnvVars need to return the same instance

Describe alternatives you’ve considered

n/a

Additional context

No response

[elyobo]

Has this been documented somewhere? I can’t find relevant docs on the site.

I also note that https://github.com/BuilderIO/qwik/issues/2138#issuecomment-1331981554 suggests more recently that useEnvData is a low level API that qwikcity developers should never have to use, but getting secrets from the server env sounds like an absolutely normal requirement that has to be done all the time - having some clarity about the recommended approach here would be great!

Vite env vars are presumably only available at dev / compilation time, not at run time, so fills a related but not quite the same niche as accessing run time environment variables.

While the decision not to support this seems to have been made, I note that SvelteKit seems to have a well thought out set of options here that distinguish between public/private and dynamic/static, so if this is revisited it might be worth looking at too.

[youngboy]

@nnelgxorz Really helpful explanation, would be great if add it to document.

And perhaps need forewarn about usage of causing leaky credentials ENV issues. In SSR mode, Vite env is convenient and accessible everywhere, https://github.com/vitejs/vite/pull/5404

like

useClientEffect$(() => {
  const env = import.meta.env
})

will resulting every env key & value exposed to JS source code in client