Astro Fixed Environment Variables!!

Never struggle with environment variables again!
Astro 4.10 Variables - astro.build/blog/astro-4100/#...
*Newsletter*
Newsletter 🗞 - www.jamesqquick.com/newsletter
*DISCORD*
Join the Learn Build Teach Discord Server 💬 - / discord
Follow me on Twitter 🐦 - / jamesqquick
Check out the Podcast - compressed.fm/
Courses - jamesqquick.com/courses
*QUESTIONS ABOUT MY SETUP*
Check out my Uses page for my VS Code setup, what recording equipment I use, etc. www.jamesqquick.com/uses

[@DennisIvy]

Saving this so I can watch later :)

[@adammatthiesen6203]

Hey James! at 4:50 The reason the public/private prefix is no longer needed, is due to the switch to utilizing Vite's loadEnv() function with a empty prefix to allow grabbing ANY of the variables. Florian actually based it off how i was doing it between my different integrations because i had been using loadEnv directly and haven't had issues. I may have been on a call with Florian debugging astro:env inside of my StudioCMS playground.... 😅

[@JamesQQuick]

hahaa good to know. Thanks for clarifying!

[@anasouardini]

Astro team is always alert to the user's problems.

[@JamesQQuick]

They're so good at that! That's why I'm so optimistic about them!

[@CyberTechBits]

Thank James! I've been trying to decide what framework (literally for years) to build with as I want to take my vanilla js app from enterprise to SaaS. Decision finally made! Astro! Next question is do I move to Svelte for the client side PWA or stick with vanilla...hmmm. Thanks again! Great channel!

[@JamesQQuick]

haha there are so many options. Astro is great though. Especially being able to leverage other UI frameworks with it. Thanks for watching!

[@hxxzxtf]

🎯 Key points for quick navigation: 00:00 *🚀 Astro has fixed environment variables, making it easier to work with them.* 00:49 *🔒 Environment variables can now be accessed at import.meta.EnV, but this has limitations such as no validation of properties or types.* 01:32 *💡 T3 dnv is a library that allows defining Zod schema for environment variables in Next.js, but Astro now has a built-in solution.* 02:16 *📁 The experimental Astro EnV module allows defining and accessing environment variables, with different use cases for client-side and server-side access.* 03:27 *🔑 The get secret function can be used to programmatically figure out what an environment variable is, but it's not necessary for most use cases.* 05:02 *🎉 The new EnV module in Astro makes working with environment variables more efficient and easier to manage.* Made with HARPA AI

[@guiltyconscious]

Good video but not trying to learn another library for a just one specific task tbh

[@theklr]

Why can’t vercel be cool like this with next 😭😭😭

[@JamesQQuick]

haha if only! It's such a good feature

[@arberstudio]

interesting

[@JamesQQuick]

Any other thoughts? Do you find it useful?

[@arberstudio]

@@JamesQQuick Insightful more so than useful as I am building a framework of my own. So yea, it’s quite insightful as I’ve been wondering about this exact type of problem and how I could handle it should I also have a server side architecture. It was great timing in my research!

[@JamesQQuick]

@@arberstudio Ah nice. Can't wait to see what you come up with!

[@yehudz]

You're thumbnails are so cringe man, much love for your video though

[@JamesQQuick]

Thanks for the feedback. What would you change?

[@yehudz]

@@JamesQQuick Be more natural, videos are great but it's not a fortnite channel you know

[@JamesQQuick]

@@yehudz I'll keep that in mind!