Why is experimental__runtimeEnv still "exprimental"

[dantman]

I just decided to try out t3-env in a test project and noticed that the documentation says:

https://env.t3.gg/docs/nextjs

 // If you're using Next.js < 13.4.4, you'll need to specify the runtimeEnv manually
 runtimeEnv: {
   DATABASE_URL: process.env.DATABASE_URL,
   OPEN_AI_API_KEY: process.env.OPEN_AI_API_KEY,
   NEXT_PUBLIC_PUBLISHABLE_KEY: process.env.NEXT_PUBLIC_PUBLISHABLE_KEY,
 },
 // For Next.js >= 13.4.4, you only need to destructure client variables:
 // experimental__runtimeEnv: {
 //   NEXT_PUBLIC_PUBLISHABLE_KEY: process.env.NEXT_PUBLIC_PUBLISHABLE_KEY,
 // }

I'm wondering why experimental__runtimeEnv is still "experimental" the version of Next.js it became usable in 13.4.4 has been out for over a year.

[juliusmarminge]

We can flip it and add a legacy instead 👍 Wanna submit a PR? We're still 0.x so breaking changes are fine ☺️

[simoami]

Hi, does legacy mean it can be omitted or does it mean to use the stable name runtimeEnv instead? And is the requirement still the same where client side environments still need to be destructured under runtimeEnv?

[juliusmarminge]

We can add a peer dep of next: >=13.4.4 and omit it altogether.

Yes, you still need manual and explicit access of client vars