Can't explicitly pass `clientPrefix` option using `nuxt`

[dammy001]

import { createEnv } from '@t3-oss/env-nuxt'
import { z } from '@bunce/schema'

export const env = createEnv({
  clientPrefix: 'NUXT_',

  client: {
    NUXT_BASE_URL: z.string().min(1),
  },
  runtimeEnv: process.env,
})

This always make use of the default NUXT_PUBLIC_

[juliusmarminge]

afaik NUXT_FOO isn't populated on client but you need to do NUXT_PUBLIC_FOO, hence the pre-configured client prefix of NUXT_PUBLIC_.

[dammy001]

@juliusmarminge What if I don't want to add PUBLIC_? I just need NUXT_. This option clientPrefix should be exposed on userland.

[juliusmarminge]

I dont think you understand what clientPrefix means. It's the thing you prefix your variabler with if you want the value sent to client. NUXT_ doesnt do that, NUXTPUBLIC does.

[dammy001]

@juliusmarminge Currently, without using t3-env my environment variables are prefixed with NUXT_ without adding PUBLIC_, and it works fine, but adding this package will result in me changing my environment variables, which I really don't want to do.

[dammy001]

@juliusmarminge i get your point now

[juliusmarminge]

Currently, without using t3-env my environment variables are prefixed with NUXT without adding PUBLIC, and it works fine

Then those should go in the server object