Stop using typescript env variables wrong

env.t3.gg/
My Products
📖 ProjectPlannerAI: projectplannerai.com
🤖 IconGeneratorAI: icongeneratorai.com
📝 ThumbnailCritique: thumbnailcritique.com
Useful Links
💬 Discord: / discord
🔔 Newsletter: newsletter.webdevcody.com/
📁 GitHub: github.com/webdevcody
📺 Twitch: / webdevcody
🤖 Website: webdevcody.com
🐦 Twitter: / webdevcody

[@Mrvituhmincguy]

Thanks for the rec as usual Cody. T3-env has worked well for me in the past

[@Stallion45]

I've seen this around but never dug into it. Just dropped it in a project. Very cool. Nice to see the quick overview. I should have used this sooner.

[@SaaSLTDDeals]

Wow, such a game-changer! Ensuring type safety for environment variables in Next.js is crucial for seamless deployment. Thanks for the tip!

[@luiswebdev8292]

super easy to implement! thank you!

[@alyahmed7639]

Great video, but this might break tree shaking, for example let's say you have isProd env variable so webpack will replace this env variables true or false and tree shaking will remove some code based on this values. one major use case if you remember redux :D you can add middlewares for dev but you don't want them in production just an example

[@anruntxd8711]

Wow thank you, I didnt know it existed!

[@kaloyangeorgiev6824]

Did I understood correctly? Using this, if on local you have all variables set it will work, but if in production you have missed for example 1 env variable or mispell it, we will get some error?

[@cloudeater9571]

Actually JUST did this type of thing recently. Many projects have limits on getting packages approved so went with a getter for env values, simple check for value and error/log otherwise. Then used the getter for each setting in a config file that the app as a whole uses to reference such values, which allows the config file to be slapped with an interface. That allows us to offset the stack overflow limitations of adding a global d.ts file for ProcessEnv with expected variables. The real kicker is googling how to do generics for the getter because ain’t nobody memorizes how :P

[@cloudeater9571]

Of note, your solution is hands down a better dev experience - kudos

[@roach_iam]

Good video, keep in mind that envs can only be strings, so don't get too carried away with the zod schemas.

[@WebDevCody]

I think this library automatically parses numbers and booleans as well

[@shigu.01]

I don't know about t3-env, but you can pass { coerce: true } into a zod number schema

[@EduarteBDO]

What if you add a test in the build process that will test all env variables, and a separate ts file that declare the env variables removing the undefined part. Then when building this test can fail and stop the build process. This would remove the dependence need. And you don't need to import {env}, I know This could be worse development experience but it could have some advantages.

[@ewwitsantonio]

Great, thank you! I have video topic suggestion: documentation creation. I'm curious what your insights me be on writing documentation for projects/tools, if that's something you do, and if there are any tools that help you to do so. Thanks!

[@WebDevCody]

I think I’ve used docsify, swagger also is good for api docs

[@ewwitsantonio]

@@WebDevCody thanks so much!

[@jorgesa4244]

What are you using now instead of t3 stack?

[@perc-ai]

supabase

[@ivanbragin7932]

Theo approved video

[@nhatvominh3387]

can someone tell me his extension theme he is using ? thanks you

[@Openbyt]

Hey, what's the VS Code theme you've got going on?

[@user-tm1xl4bf7o]

did you find??

[@user-tm1xl4bf7o]

Bearded theme stained blue

[@user-jm1qz4dj9l]

Can you show all your extensions?

[@Support-Phalestine]

bro can you guide me is it valuable to learn c# .netcore at this time is it worth it or not ??

[@WebDevCody]

I’ve never had a .net job, but I know there are jobs using both

[@Dom-zy1qy]

I am assuming .net would be a bit better for job prospects, seems less competitive than js world. I really am just guessing tho.

[@Support-Phalestine]

@@Dom-zy1qy exactly bro that's the point

[@AneeshSaravuKarekad]

Is environment validation in runtime really necessary just to get type inference? I would rather move the env validation to a build step before deploying. Let me know your thoughts. Great work on the consistency!

[@WebDevCody]

It’s just a little extra help to consolidate all env variables. I’ve been on apps where the same env variable is imported in like 10 files; this helps centralize the config a bit

[@AneeshSaravuKarekad]

@@WebDevCody Ah I do suggest having a centralized config file for environment variables, but I don't like running validation on the config in runtime.

[@SeibertSwirl]

Good job babe!

[@WebDevCody]

😘

[@Openbyt]

Please tell me What is your vs code theme name? Sir

[@iiilllii140]

Does it only work with zod? My project uses valibot.

[@theklr]

They have work in progress to decouple the validator.

[@tsykin]

I usually just create utils file where I define and export object with all env.process strings to then reference them in other files. Do you think that's smart or not really?

[@WebDevCody]

Seems ok to me

[@qizhang5749]

I use joi and make a schema for my environment variables

[@filipfiser1045]

Cool package, but I don't know about having so much packages inside my project. I already have a lot.

[@plusquare]

typesafe env vars are great until u forgot to update the env vars for CI and that shit breaks anyway

[@flyingpanhandle]

you really don't need multiple third party libs to do this.

[@WebDevCody]

Multiple? Who uses multiple?

[@flyingpanhandle]

@@WebDevCody 1. T3-env. 2. Zod.

[@WebDevCody]

@@flyingpanhandle oh I see what you mean

[@user-pj4ju1oi1l]

@flyingpanhandle Could you give an example without third party libs? Or do you mean only T3-env lib is necessary to achieve something similar.

[@theklr]

Can you give solutions?