Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error with shared vars on client #280

Closed
chertik77 opened this issue Oct 28, 2024 · 2 comments
Closed

Error with shared vars on client #280

chertik77 opened this issue Oct 28, 2024 · 2 comments

Comments

@chertik77
Copy link

import { createEnv } from '@t3-oss/env-nextjs'
import { z } from 'zod'

export const env = createEnv({
  shared: {
    EXAMPLE_VAR: z.string()
  },
  experimental__runtimeEnv: {
    EXAMPLE_VAR: process.env.EXAMPLE_VAR
  }
})

I'm getting var on server successfully, but always getting error on client side, what's wrong?

Screenshot 2024-10-28 at 21 42 09

@chertik77 chertik77 changed the title Error with shared vars Error with shared vars on client Oct 28, 2024
@criskell
Copy link

Try importing with NEXT_PUBLIC_ prefix.
Worked with me.

@juliusmarminge
Copy link
Member

t3-env doesn't do anything in your build process to make these available on the client. what this field is for is to have access to a variable that's not prefixed with the (for example) NEXT_PUBLIC prefix on the client. NODE_ENV is more an exception than rule here. If you want to statically replace this EXAMPLE_VAR on the client during build you'll need to set that in nextConfig#env. Read more here: https://nextjs.org/docs/app/api-reference/config/next-config-js/env

t3-env is validation only. Hope this clarifies it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants