An Hoang

Actually I don't see any `import.meta.env` after build, because Vite is supposed to replace those statically at build time. `@astrojs/cloudflare` as far as I can see doesn't have anything to...

> > pass getRuntime().env to t3-env's runtimeEnv somehow for each request > > That is correct, however not sure if that is possible & if that would work on initial...

I updated the original issue with my new setup. There were some misunderstandings of the Vite build step, so I documented the correct behavior in the code. As for @alexanderniebuhr's...

1st problem about `process`: Might be because the code is accessing `process` on the client, which is in turn because the code (the t3-env Nuxt package) forgot to treat the...

Tried searching for my server variables in the client bundles. Indeed I can see my build-time server-side variables leaked in the bundle, but all the runtime server-side variables are not...

Lesson learned: One must build the project, then go to the DevTools and search for their envs on the client, just to be sure. Maybe even inspect the server bundle...

> Can you explain what variables are leaked and how? The framework shouldn't let server-side variables be defined on the client, no matter what file you're using it in. There...