https://tube.grossholtz.net/videos/watch/00f494ca-39ce-42a2-97de-c03afccabce7 🎬Finally your app is in production - amazing! But how can we ensure that certain configurations or even whole modules are only loaded in dev, or only in production? Would it be even possible to change the nuxt configuration for test environments? A common way is using process.env.NODE_ENV - but luckily, Nuxt provides a more descriptive and foolproof way, which is shown in this video! Key points: ✨ How to make your config env-aware 🛠 When and why Nuxt influences your node env set 💡 Examples how to set parts of the config depending on the env 👀 Exploring the underlying package Links: 🔗 c12 - https://github.com/unjs/c12 📺 Runtime Config Mistake - https://www.youtube.com/watch?v=_FYV5WfiWvs Don't forget to hit that "Subscribe" button, ring the notification bell and give a thumbs up! 🌐 Connect further: Website: https://www.lichter.io Twitter/X: https://twitter.com/TheAlexLichter Twitch: https://www.twitch.tv/TheAlexLichter Chapters: 00:00 Intro and agenda 00:48 Demo app overview 01:20 Setting up the tab title for the application 02:32 Changing the value in development only 04:47 Do the same but for production 05:13 How Nuxt changes the NODE ENV 06:13 Taking a look at the prod build 06:46 How this works under the hood - A look at c12 08:45 Summary Mon, 06 Apr 2026 05:06:59 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://tube.grossholtz.net https://tube.grossholtz.net/client/assets/images/icons/icon-512x512.png https://tube.grossholtz.net/videos/watch/00f494ca-39ce-42a2-97de-c03afccabce7 All rights reserved, unless otherwise specified in the terms specified at https://tube.grossholtz.net/about and potential licenses granted by each content's rightholder.