consider allowing string | boolean | undefined for runtimeEnvStrict

[stefanprobst]

when using this package with nuxt to type VITE_ env vars, i am running into the following issue: nuxt types import.meta.env as Record<string, string | boolean | undefined> (see here) - i am guessing because vite sets these default values. however, t3-env enforces runtimeEnvStrict to be Record<string, string | undefined>. would you consider allowing Record<string, string | boolean | undefined> on runtimeEnvStrict to cover this usecase?

[juliusmarminge]

That's a strange one - never seen that... environment variables are usually just strings...

I guess it'd fine? Although would love to know why this typedefinition is what it is to begin with, and why they don't use "0" and "1" like everyone else 🤔

[chungweileong94]

From what I can tell, it's no longer the case vitejs/vite#7702 in vite.
There're only two possible reasons I can think of:

• it's either nuxt team forgot to fix the type.
• nuxt has some sort of parser for parsing the boolean-like values.

[chungweileong94]

TBH, I don't think it's a bad idea to define the type as any, since it has runtimeEnv config, which means the value can be anything other than process.env, plus it's all about zod validation anyway.

[juliusmarminge]

i guess