Astro Fixed Environment Variables!! 

Saving this so I can watch later :)

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

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.... 😅

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!

🎯 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

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

interesting

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

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