Denis Krylov
282eb87e63
Some checks failed
Deploy monie-landing (kaniko) / build-and-deploy (push) Failing after 20m45s
40 lines
1.2 KiB
TypeScript
40 lines
1.2 KiB
TypeScript
import { createEnv } from "@t3-oss/env-core";
|
|
import { z } from "zod";
|
|
|
|
export const env = createEnv({
|
|
server: {
|
|
SERVER_URL: z.string().url().optional(),
|
|
},
|
|
|
|
/**
|
|
* The prefix that client-side variables must have. This is enforced both at
|
|
* a type-level and at runtime.
|
|
*/
|
|
clientPrefix: "VITE_",
|
|
|
|
client: {
|
|
VITE_APP_TITLE: z.string().min(1).optional(),
|
|
},
|
|
|
|
/**
|
|
* What object holds the environment variables at runtime. This is usually
|
|
* `process.env` or `import.meta.env`.
|
|
*/
|
|
runtimeEnv: import.meta.env,
|
|
|
|
/**
|
|
* By default, this library will feed the environment variables directly to
|
|
* the Zod validator.
|
|
*
|
|
* This means that if you have an empty string for a value that is supposed
|
|
* to be a number (e.g. `PORT=` in a ".env" file), Zod will incorrectly flag
|
|
* it as a type mismatch violation. Additionally, if you have an empty string
|
|
* for a value that is supposed to be a string with a default value (e.g.
|
|
* `DOMAIN=` in an ".env" file), the default value will never be applied.
|
|
*
|
|
* In order to solve these issues, we recommend that all new projects
|
|
* explicitly specify this option as true.
|
|
*/
|
|
emptyStringAsUndefined: true,
|
|
});
|