By default, Nuxt is configured to cover most use cases. The nuxt.config.ts file can override or extend this default configuration.

Nuxt Configuration

The nuxt.config.ts file is located at the root of a Nuxt project and can override or extend the application's behavior.

A minimal configuration file exports the defineNuxtConfig function containing an object with your configuration. The defineNuxtConfig helper is globally available without import.

export default defineNuxtConfig({  // My Nuxt config})

This file will often be mentioned in the documentation, for example to add custom scripts, register modules or change rendering modes.

Every configuration option is described in the Configuration Reference.
You don't have to use TypeScript to build an application with Nuxt. However, it is strongly recommended to use the .ts extension for the nuxt.config file. This way you can benefit from hints in your IDE to avoid typos and mistakes while editing your configuration.

Environment Variables and Private Tokens

The runtimeConfig API exposes values like environment variables to the rest of your application. By default, these keys are only available server-side. The keys within runtimeConfig.public are also available client-side.

Those values should be defined in nuxt.config and can be overridden using environment variables.

export default defineNuxtConfig({  runtimeConfig: {    // The private keys which are only available server-side    apiSecret: '123',    // Keys within public are also exposed client-side    public: {      apiBase: '/api'    }  }})
# This will override the value of apiSecret

These variables are exposed to the rest of your application using the useRuntimeConfig composable.

<script setup>const runtimeConfig = useRuntimeConfig()</script>

App Configuration

The app.config.ts file, also located at the root of a Nuxt project, is used to expose public variables that can be determined at build time. Contrary to the runtimeConfig option, these can not be overriden using environment variables.

A minimal configuration file exports the defineAppConfig function containing an object with your configuration. The defineAppConfig helper is globally available without import.

export default defineAppConfig({  title: 'Hello Nuxt',  theme: {    dark: true,    colors: {      primary: '#ff0000'    }  }})

These variables are exposed to the rest of your application using the useAppConfig composable.

<script setup>const appConfig = useAppConfig()</script>

runtimeConfig vs app.config

As stated above, runtimeConfig and app.config are both used to expose variables to the rest of your application. To determine whether you should use one or the other, here are some guidelines:

  • runtimeConfig: Private or public tokens that need to be specified after build using environment variables.
  • app.config : Public tokens that are determined at build time, website configuration such as theme variant, title and any project config that are not sensitive.
Client SideHydratedBundled
Environment Variables✅ Yes❌ No
Reactive✅ Yes✅ Yes
Types support✅ Partial✅ Yes
Configuration per Request❌ No✅ Yes
Hot Module Replacement❌ No✅ Yes
Non primitive JS types❌ No✅ Yes

External Configuration Files

Nuxt uses nuxt.config.ts file as the single source of trust for configurations and skips reading external configuration files. During the course of building your project, you may have a need to configure those. The following table highlights common configurations and, where applicable, how they can be configured with Nuxt.

NameConfig FileHow To Configure
Nitronitro.config.tsUse nitro key in nuxt.config
PostCSSpostcss.config.jsUse postcss key in nuxt.config
Vitevite.config.tsUse vite key in nuxt.config
webpackwebpack.config.tsUse webpack key in nuxt.config

Here is a list of other common config files:

NameConfig FileHow To Configure
Typescipttsconfig.jsonMore Info
ESLint.eslintrc.jsMore Info
Prettier.prettierrc.jsonMore Info
Stylelint.stylelintrc.jsonMore Info
TailwindCSStailwind.config.jsMore Info
Vitestvitest.config.tsMore Info