Chung Wei Leong
Chung Wei Leong
For some reason, this feature doesn't really work on Zed Preview 0.137.0.
> This may already be fixed, have u tried the latest preview builds? At least I am not seeing this anymore.. I got the same conclusion, haven't seen it for...
It's possible right now, but not the way you expected. ```ts import { createEnv as createT3Env } from "@t3-oss/env-core"; import { z } from "zod"; async function loadEnv() { const...
@julius-retzer If you are working in the server-only environment, the `server` option is all you need, and you can just ignore the `clientPrefix` & `client` options. However, one gotcha is...
> 1. What "server" and "client" namespaces mean precisely? Is React RSC a "server" or a "client"? Is NextJS middleware a "server"? I assume it's all "server" because it's executed...
> with `Attempted to access a server-side environment variable on the client` as mentioned by the topic starter. > Why it's suddendly a "server side variable"? 👀 When you try...
> so I don't get the purpose of a framework-specific ENV naming. It feels bad to declare the same var as, for example, NEXT_PUBLIC_APP_ORIGIN in NextJS and APP_ORIGIN elsewhere. It's...
That can be really useful! As of now, you can actually use both `dotenv` & `t3-env` in `drizzle.config.ts` as a workaround.
> Can i implement it in rust? I don't have much experience with Rust, might be a bit overkill for simple feature like this, but I guess so? @juliusmarminge
Yeah, TS would be better, CI is a lot easy to setup.