feat: make runtimeEnv optional in Next.js and default to process.env

[juliusmarminge]

Closes #71

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
t3-env	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 25, 2023 3:45pm

[github-actions]

A new canary is available for testing. You can install this latest build in your project with:

pnpm add @t3-oss/env-core@0.4.1-canary.40f9204

or, if you're using Next.js:

pnpm add @t3-oss/env-nextjs@0.4.1-canary.40f9204

or, if you're using Nuxt:

pnpm add @t3-oss/env-nuxt@0.4.1-canary.40f9204

[juliusmarminge]

Hmm client variables are not automatically defined 🤔

[juliusmarminge]

@chungweileong94 What do you think of this?

[github-actions]

A new canary is available for testing. You can install this latest build in your project with:

pnpm add @t3-oss/env-core@0.4.2-canary.6984043

or, if you're using Next.js:

pnpm add @t3-oss/env-nextjs@0.4.2-canary.6984043

or, if you're using Nuxt:

pnpm add @t3-oss/env-nuxt@0.4.2-canary.6984043

[chungweileong94]

@chungweileong94 What do you think of this?

LGTM, even though the experimental__runtimeEnv looks a bit ambiguous, and I can't think of anything else as of now. But things could be changed/improved overtime, especially if Vercel decided to do the same thing on client🤞