Multi-client prefixes

[renaldodev]

Its not a real issue but a question.

Is there some way to use multi-client prefixes?

I'm working on monorepo project and I'm using they both NextJS application and Expo application. I'd like to you 'EXPO_PUBLIC_' and 'NEXT_PUBLIC_' at the same time.

[EskiMojo14]

currently i don't think this is possible - but I've just checked and #316 makes it so each env can have their own client prefix and it'll still be handled correctly:

const expoEnv = createEnv({
  // ...
  clientPrefix: "EXPO_PUBLIC_"
})

const nextEnv = createEnv({
  // ..
  clientPrefix: "NEXT_PUBLIC_",
  extends: [expoEnv]
})

[Bartek532]

Hey!

I just released a library that might be a great fit for your use case - it's a drop-in replacement for the one you're currently using, with some extra features like a built-in CLI and live preview:

🔗 https://envin.turbostarter.dev/

Feel free to reach out if you have any questions or suggestions - every bit of feedback is welcome! 🔥

[EskiMojo14]

@Bartek532 spamming multiple issues advertising your library is not a good way to build good will, especially if much of the code is directly taken from t3-env (allowed by the license but still a bit of a dick move, especially combined with the spamming).

[Bartek532]

@EskiMojo14 got it, you're absolutely right, I just put the comment on the issues that I fixed in my implementation. Also, I agree that some of the code is taken from this library, because I found it a solid foundation to build on top of it, maybe we can somehow collaborate and manage to put everything into one library (including cli, live preview etc.) to avoid doing the same work twice? What do you think?