don't restrict to strings

.changeset/gentle-ears-dance.md

@@ -0,0 +1,7 @@
+---
+"@t3-oss/env-core": minor
+---
+
+don't restrict runtimeEnv to just strings
+
+turns out some frameworks inject environment variables as booleans or numbers, this allows you to use those without getting type errors

packages/core/index.ts

@@ -69,7 +69,7 @@ export interface LooseOptions<
    * Runtime Environment variables to use for validation - `process.env`, `import.meta.env` or similar.
    * Unlike `runtimeEnvStrict`, this doesn't enforce that all environment variables are set.
    */
-  runtimeEnv: Record<string, string | undefined>;
+  runtimeEnv: Record<string, string | boolean | number | undefined>;
 }
 
 export interface StrictOptions<
@@ -88,7 +88,7 @@ export interface StrictOptions<
           : never;
       }[keyof TClient]
     | keyof TServer,
-    string | undefined
+    string | boolean | number | undefined
   >;
   runtimeEnv?: never;
 }

packages/core/test/smoke.test.ts

@@ -144,6 +144,31 @@ describe("return type is correctly inferred", () => {
   });
 });
 
+test("can pass number and booleans", () => {
+  const env = createEnv({
+    clientPrefix: "FOO_",
+    server: {
+      PORT: z.number(),
+      IS_DEV: z.boolean(),
+    },
+    client: {},
+    runtimeEnvStrict: {
+      PORT: 123,
+      IS_DEV: true,
+    },
+  });
+
+  expectTypeOf(env).toEqualTypeOf<{
+    PORT: number;
+    IS_DEV: boolean;
+  }>();
+
+  expect(env).toMatchObject({
+    PORT: 123,
+    IS_DEV: true,
+  });
+});
+
 describe("errors when validation fails", () => {
   test("envs are missing", () => {
     expect(() =>