github.com/bentsignal/convex-env @v3.0.0

Convex Env

Type-safe access to environment variables in Convex

Overview

Similar to t3-env, but native to Convex.

Validators currently supported:

• v.string()
• v.number()
• v.boolean()
• v.union() + v.literal() (strings only)

You can use v.optional() on any supported validator, see examples below

IMPORTANT: The env object from createEnv should only be used in the Convex runtime, the values on it will not be accessible client-side.

Installation

ni convex-env

pnpm i convex-env

bun i convex-env

npm i convex-env

yarn add convex-env

Usage

// convex/convex.env.ts

import { createEnv } from "convex-env";
import { betterAuth, oAuth } from "convex-env/presets";
import { v } from "convex/values";

export const env = createEnv({
  ...betterAuth,
  ...oAuth.google,
  ENVIRONMENT: v.union(v.literal("development"), v.literal("production")),
  OPENAI_API_KEY: v.string(),
  GOOGLE_CLIENT_SECRET: v.string(),
  FREE_REQUESTS_PER_USER: v.number(),
  DEBUG_MODE: v.optional(v.boolean()),
});

Then access them anywhere in Convex.

// convex/auth.ts

import { env } from "./convex.env";

export const createAuth = (ctx: GenericCtx<DataModel>) => {
  return betterAuth({
    baseURL: env.CONVEX_SITE_URL,
    socialProviders: {
      google: {
        clientId: env.GOOGLE_CLIENT_ID,
        clientSecret: env.GOOGLE_CLIENT_SECRET,
      },
    },
  });
};

You can optionally pass values manually

// convex/convex.env.ts

import { createEnv } from "convex-env";
import { v } from "convex/values";

export const env = createEnv({
  schema: {
    FREE_REQUESTS_PER_USER: v.number(),
    DEBUG_MODE: v.optional(v.boolean()),
  },
  // optional, defaults to process.env
  values: {
    FREE_REQUESTS_PER_USER: process.env.FREE_REQUESTS_PER_USER,
    DEBUG_MODE: process.env.DEBUG_MODE,
  },
});

If you're running into an issue where it says an environment variable isn't found when you know for a fact that it is there, then you may need to use verifyEnv to verify the existence and type separately from the creation of the env object.

// convex/convex.env.ts

import { createEnv } from "convex-env";
import { v } from "convex/values";

export const schema = {
  FREE_REQUESTS_PER_USER: v.number(),
  DEBUG_MODE: v.optional(v.boolean()),
};

export const env = createEnv({
  schema,
  options: {
    skipValidation: true,
  },
});

// convex/convex.config.ts

import { schema } from "./convex.env";
import { verifyEnv } from "convex-env";

verifyEnv(schema);

Presets

I wrote out some presets for commonly used pairs of variables. Below is a complete list of all exports from convex-env/presets.

• oAuth
• everything supported by better-auth
• environment
• "development", "preview", or "production"
• aws
• clerk
• workOS,
• betterAuth
• auth0
• resend
• r2
• stripe
• autumn
• dodo
• polar
• uploadthing
• upstash

// convex/convex.env.ts

import { createEnv } from "convex-env";
import { oAuth, betterAuth, polar, r2 } from "convex-env/presets";

export const env = createEnv({
  ...betterAuth,
  ...oAuth.google,
  ...oAuth.github,
  ...polar,
  ...r2,
  OPENAI_API_KEY: v.string(),
  FREE_REQUESTS_PER_USER: v.number(),
  DEBUG_MODE: v.optional(v.boolean()),
});

Why use it?

User defined values on the process.env object will always be typed string | undefined. If you want to store anything other than a string, you have to cast it at each use and hope that you entered the value correctly in .env

This package gives you the reassurance that when you use an environment variable in your code, it will:

• Actually be there
• Be the type you expect it to be

It can also prevent you from shipping bugs to production. If an environment variable is missing or doesn't match its validator, your deployment to Convex will fail.