It sometimes happens that you need to have different configurations for different environments in your Nuxt.js application. In this article, I'll show you how to use environment-specific Nuxt configurations.
Let's start with a simple nuxt.config.ts file:
For demonstration purposes, let's assume that we want to have a different title in development and production. You might be tempted to use an environment variable like this:
This approach is not recommended by Nuxt, instead, you should use the fully typed, per-environment overrides like $production, $development or $test in your nuxt.config file. Here's how you can do it:
The $development key is a special key that allows you to define a Nuxt configuration for the development environment. This configuration is merged with the default configuration when running in development mode. This mechanism is powered by c12, a smart configuration loader available in the UnJS ecosystem.
Info
If you're authoring layers, you can also use the $meta key to provide metadata that you or the consumers of your layer might use.
If you liked this Vue tip, follow me on X to get notified about new tips, blog posts, and more. Alternatively (or additionally), you can subscribe to my weekly Vue & Nuxt newsletter:
Vue Tip: Validate Props in Script Setup With TypeScript
For prop validations inside `<script setup>` with TypeScript you need to define an interface for the props and use the `withDefaults` helper to set default values.
Vue Tip: Share Styling Using Wrapper Components
Wrapper components can help you share styling across multiple Vue components. This can make your code cleaner and more maintainable.