@nuxt/docs 4.1.1 → 4.1.3

package/2.guide/{2.directory-structure → 1.directory-structure}/1.content.md

@@ -2,10 +2,10 @@
 title: 'content'
 head.title: 'content/'
 description: Use the content/ directory to create a file-based CMS for your application.
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-log
 ---
 
-[Nuxt Content](https://content.nuxt.com) reads the [`content/` directory](/docs/guide/directory-structure/content) in your project and parses `.md`, `.yml`, `.csv` and `.json` files to create a file-based CMS for your application.
+[Nuxt Content](https://content.nuxt.com) reads the [`content/` directory](/docs/4.x/guide/directory-structure/content) in your project and parses `.md`, `.yml`, `.csv` and `.json` files to create a file-based CMS for your application.
 
 - Render your content with built-in components.
 - Query your content with a MongoDB-like API.
@@ -36,7 +36,7 @@ The module automatically loads and parses them.
 
 ## Render Content
 
-To render content pages, add a [catch-all route](/docs/guide/directory-structure/app/pages/#catch-all-route) using the [`<ContentRenderer>`](https://content.nuxt.com/docs/components/content-renderer) component:
+To render content pages, add a [catch-all route](/docs/4.x/guide/directory-structure/app/pages/#catch-all-route) using the [`<ContentRenderer>`](https://content.nuxt.com/docs/components/content-renderer) component:
 
 ```vue [app/pages/[...slug\\].vue]
 <script lang="ts" setup>
@@ -50,7 +50,10 @@ const { data: page } = await useAsyncData(route.path, () => {
   <div>
     <header><!-- ... --></header>
 
-    <ContentRenderer v-if="page" :value="page" />
+    <ContentRenderer
+      v-if="page"
+      :value="page"
+    />
 
     <footer><!-- ... --></footer>
   </div>

package/2.guide/{2.directory-structure → 1.directory-structure}/1.modules.md

@@ -2,7 +2,7 @@
 title: 'modules'
 head.title: 'modules/'
 description: Use the modules/ directory to automatically register local modules within your application.
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-nuxt
 ---
 
 It is a good place to place any local modules you develop while building your application.
@@ -11,18 +11,18 @@ The auto-registered files patterns are:
 - `modules/*/index.ts`
 - `modules/*.ts`
 
-You don't need to add those local modules to your [`nuxt.config.ts`](/docs/guide/directory-structure/nuxt-config) separately.
+You don't need to add those local modules to your [`nuxt.config.ts`](/docs/4.x/guide/directory-structure/nuxt-config) separately.
 
 ::code-group
 
 ```ts twoslash [modules/hello/index.ts]
 // `nuxt/kit` is a helper subpath import you can use when defining local modules
 // that means you do not need to add `@nuxt/kit` to your project's dependencies
-import { createResolver, defineNuxtModule, addServerHandler } from 'nuxt/kit'
+import { addServerHandler, createResolver, defineNuxtModule } from 'nuxt/kit'
 
 export default defineNuxtModule({
   meta: {
-    name: 'hello'
+    name: 'hello',
   },
   setup () {
     const resolver = createResolver(import.meta.url)
@@ -30,9 +30,9 @@ export default defineNuxtModule({
     // Add an API route
     addServerHandler({
       route: '/api/hello',
-      handler: resolver.resolve('./runtime/api-route')
+      handler: resolver.resolve('./runtime/api-route'),
     })
-  }
+  },
 })
 ```
 
@@ -47,7 +47,7 @@ export default defineEventHandler(() => {
 When starting Nuxt, the `hello` module will be registered and the `/api/hello` route will be available.
 
 Modules are executed in the following sequence:
-- First, the modules defined in [`nuxt.config.ts`](/docs/api/nuxt-config#modules-1) are loaded.
+- First, the modules defined in [`nuxt.config.ts`](/docs/4.x/api/nuxt-config#modules-1) are loaded.
 - Then, modules found in the `modules/` directory are executed, and they load in alphabetical order.
 
 You can change the order of local module by adding a number to the front of each directory name:
@@ -59,7 +59,7 @@ modules/
   2.second-module.ts
 ```
 
-:read-more{to="/docs/guide/going-further/modules"}
+:read-more{to="/docs/4.x/guide/going-further/modules"}
 
 ::tip{icon="i-lucide-video" to="https://vueschool.io/lessons/creating-your-first-module-from-scratch?friend=nuxt" target="_blank"}
 Watch Vue School video about Nuxt private modules.

package/2.guide/{2.directory-structure → 1.directory-structure}/1.node_modules.md

@@ -2,11 +2,11 @@
 title: "node_modules"
 description: "The package manager stores the dependencies of your project in the node_modules/ directory."
 head.title: "node_modules/"
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-node
 ---
 
 The package manager ([`npm`](https://docs.npmjs.com/cli/commands/npm) or [`yarn`](https://yarnpkg.com) or [`pnpm`](https://pnpm.io/cli/install) or [`bun`](https://bun.sh/package-manager)) creates this directory to store the dependencies of your project.
 
 ::important
-This directory should be added to your [`.gitignore`](/docs/guide/directory-structure/gitignore) file to avoid pushing the dependencies to your repository.
+This directory should be added to your [`.gitignore`](/docs/4.x/guide/directory-structure/gitignore) file to avoid pushing the dependencies to your repository.
 ::

package/2.guide/{2.directory-structure → 1.directory-structure}/1.public.md

@@ -2,7 +2,7 @@
 title: "public"
 description: "The public/ directory is used to serve your website's static assets."
 head.title: "public/"
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-public
 ---
 
 Files contained within the `public/` directory are served at the root and are not modified by the build process. This is suitable for files that have to keep their names (e.g. `robots.txt`) _or_ likely won't change (e.g. `favicon.ico`).
@@ -17,7 +17,7 @@ Files contained within the `public/` directory are served at the root and are no
 ```vue [app/app.vue]
 <script setup lang="ts">
 useSeoMeta({
-  ogImage: '/og-image.png'
+  ogImage: '/og-image.png',
 })
 </script>
 ```

package/2.guide/{2.directory-structure → 1.directory-structure}/1.server.md

@@ -2,7 +2,7 @@
 title: server
 head.title: 'server/'
 description: The server/ directory is used to register API and server handlers to your application.
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-server
 ---
 
 Nuxt automatically scans files inside these directories to register API and server handlers with Hot Module Replacement (HMR) support.
@@ -24,7 +24,7 @@ The handler can directly return JSON data, a `Promise`, or use `event.node.res.e
 ```ts twoslash [server/api/hello.ts]
 export default defineEventHandler((event) => {
   return {
-    hello: 'world'
+    hello: 'world',
   }
 })
 ```
@@ -58,7 +58,7 @@ export default defineEventHandler(() => 'Hello World!')
 Given the example above, the `/hello` route will be accessible at <http://localhost:3000/hello>.
 
 ::note
-Note that currently server routes do not support the full functionality of dynamic routes as [pages](/docs/guide/directory-structure/app/pages#dynamic-routes) do.
+Note that currently server routes do not support the full functionality of dynamic routes as [pages](/docs/4.x/guide/directory-structure/app/pages#dynamic-routes) do.
 ::
 
 ## Server Middleware
@@ -115,9 +115,9 @@ For example, you can define a custom handler utility that wraps the original han
 import type { EventHandler, EventHandlerRequest } from 'h3'
 
 export const defineWrappedResponseHandler = <T extends EventHandlerRequest, D> (
-  handler: EventHandler<T, D>
+  handler: EventHandler<T, D>,
 ): EventHandler<T, D> =>
-  defineEventHandler<T>(async event => {
+  defineEventHandler<T>(async (event) => {
     try {
       // do something before the route handler
       const response = await handler(event)
@@ -234,10 +234,10 @@ You can now universally call this API using:
 
 ```vue [app/app.vue]
 <script setup lang="ts">
-async function submit() {
+async function submit () {
   const { body } = await $fetch('/api/submit', {
     method: 'post',
-    body: { test: 123 }
+    body: { test: 123 },
   })
 }
 </script>
@@ -269,11 +269,11 @@ If no errors are thrown, a status code of `200 OK` will be returned.
 
 Any uncaught errors will return a `500 Internal Server Error` HTTP Error.
 
-To return other error codes, throw an exception with [`createError`](/docs/api/utils/create-error):
+To return other error codes, throw an exception with [`createError`](/docs/4.x/api/utils/create-error):
 
 ```ts [server/api/validation/[id\\].ts]
 export default defineEventHandler((event) => {
-  const id = parseInt(event.context.params.id) as number
+  const id = Number.parseInt(event.context.params.id) as number
 
   if (!Number.isInteger(id)) {
     throw createError({
@@ -287,7 +287,7 @@ export default defineEventHandler((event) => {
 
 ### Status Codes
 
-To return other status codes, use the [`setResponseStatus`](/docs/api/utils/set-response-status) utility.
+To return other status codes, use the [`setResponseStatus`](/docs/4.x/api/utils/set-response-status) utility.
 
 For example, to return `202 Accepted`
 
@@ -306,8 +306,8 @@ export default defineEventHandler(async (event) => {
 
   const repo = await $fetch('https://api.github.com/repos/nuxt/nuxt', {
     headers: {
-      Authorization: `token ${config.githubToken}`
-    }
+      Authorization: `token ${config.githubToken}`,
+    },
   })
 
   return repo
@@ -316,8 +316,8 @@ export default defineEventHandler(async (event) => {
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
   runtimeConfig: {
-    githubToken: ''
-  }
+    githubToken: '',
+  },
 })
 ```
 ```ini [.env]
@@ -326,7 +326,7 @@ NUXT_GITHUB_TOKEN='<my-super-token>'
 ::
 
 ::note
-Giving the `event` as argument to `useRuntimeConfig` is optional, but it is recommended to pass it to get the runtime config overwritten by [environment variables](/docs/guide/going-further/runtime-config#environment-variables) at runtime for server routes.
+Giving the `event` as argument to `useRuntimeConfig` is optional, but it is recommended to pass it to get the runtime config overwritten by [environment variables](/docs/4.x/guide/going-further/runtime-config#environment-variables) at runtime for server routes.
 ::
 
 ### Request Cookies
@@ -363,8 +363,8 @@ The `event.waitUntil` method accepts a promise that will be awaited before the h
 
 ```ts [server/api/background-task.ts]
 const timeConsumingBackgroundTask = async () => {
-  await new Promise((resolve) => setTimeout(resolve, 1000))
-};
+  await new Promise(resolve => setTimeout(resolve, 1000))
+}
 
 export default eventHandler((event) => {
   // schedule a background task without blocking the response
@@ -372,7 +372,7 @@ export default eventHandler((event) => {
 
   // immediately send the response to the client
   return 'done'
-});
+})
 ```
 
 ## Advanced Usage
@@ -388,11 +388,11 @@ This is an advanced option. Custom config can affect production deployments, as
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
   // https://nitro.build/config
-  nitro: {}
+  nitro: {},
 })
 ```
 
-:read-more{to="/docs/guide/concepts/server-engine"}
+:read-more{to="/docs/4.x/guide/concepts/server-engine"}
 
 ### Nested Router
 
@@ -454,7 +454,7 @@ Never combine `next()` callback with a legacy middleware that is `async` or retu
 
 ### Server Storage
 
-Nitro provides a cross-platform [storage layer](https://nitro.build/guide/storage). In order to configure additional storage mount points, you can use `nitro.storage`, or [server plugins](#server-plugins).
+Nitro provides a cross-platform [storage layer](https://nitro.build/guide/storage). In order to configure additional storage mount points, you can use `nitro.storage`, or [server plugins](/docs/4.x/guide/directory-structure/server#server-plugins).
 
 **Example of adding a Redis storage:**
 
@@ -468,14 +468,14 @@ export default defineNuxtConfig({
         driver: 'redis',
         /* redis connector options */
         port: 6379, // Redis port
-        host: "127.0.0.1", // Redis host
-        username: "", // needs Redis >= 6
-        password: "",
+        host: '127.0.0.1', // Redis host
+        username: '', // needs Redis >= 6
+        password: '',
         db: 0, // Defaults to 0
-        tls: {} // tls/ssl
-      }
-    }
-  }
+        tls: {}, // tls/ssl
+      },
+    },
+  },
 })
 ```
 
@@ -511,11 +511,11 @@ export default defineNitroPlugin(() => {
 
   // Dynamically pass in credentials from runtime configuration, or other sources
   const driver = redisDriver({
-      base: 'redis',
-      host: useRuntimeConfig().redis.host,
-      port: useRuntimeConfig().redis.port,
-      /* other redis connector options */
-    })
+    base: 'redis',
+    host: useRuntimeConfig().redis.host,
+    port: useRuntimeConfig().redis.port,
+    /* other redis connector options */
+  })
 
   // Mount driver
   storage.mount('redis', driver)
@@ -529,8 +529,8 @@ export default defineNuxtConfig({
       host: '',
       port: 0,
       /* other redis connector options */
-    }
-  }
+    },
+  },
 })
 ```
 ::

package/2.guide/{2.directory-structure → 1.directory-structure}/1.shared.md

@@ -2,7 +2,7 @@
 title: 'shared'
 head.title: 'shared/'
 description: 'Use the shared/ directory to share functionality between the Vue app and the Nitro server.'
-navigation.icon: i-lucide-folder
+navigation.icon: i-vscode-icons-folder-type-shared
 ---
 
 The `shared/` directory allows you to share code that can be used in both the Vue app and the Nitro server.
@@ -35,7 +35,7 @@ export default function (input: string) {
 }
 ```
 
-You can now use [auto-imported](/docs/guide/directory-structure/shared#auto-imports) utilities in your Nuxt app and `server/` directory.
+You can now use [auto-imported](/docs/4.x/guide/directory-structure/shared) utilities in your Nuxt app and `server/` directory.
 
 ```vue [app/app.vue]
 <script setup lang="ts">
@@ -52,7 +52,7 @@ const hello = capitalize('hello')
 ```ts [server/api/hello.get.ts]
 export default defineEventHandler((event) => {
   return {
-    hello: capitalize('hello')
+    hello: capitalize('hello'),
   }
 })
 ```
@@ -62,10 +62,10 @@ export default defineEventHandler((event) => {
 Only files in the `shared/utils/` and `shared/types/` directories will be auto-imported. Files nested within subdirectories of these directories will not be auto-imported unless you add these directories to `imports.dirs` and `nitro.imports.dirs`.
 
 ::tip
-The way `shared/utils` and `shared/types` auto-imports work and are scanned is identical to the [`app/composables/`](/docs/guide/directory-structure/app/composables) and [`app/utils/`](/docs/guide/directory-structure/app/utils) directories.
+The way `shared/utils` and `shared/types` auto-imports work and are scanned is identical to the [`app/composables/`](/docs/4.x/guide/directory-structure/app/composables) and [`app/utils/`](/docs/4.x/guide/directory-structure/app/utils) directories.
 ::
 
-:read-more{to="/docs/guide/directory-structure/app/composables#how-files-are-scanned"}
+:read-more{to="/docs/4.x/guide/directory-structure/app/composables#how-files-are-scanned"}
 
 ```bash [Directory Structure]
 -| shared/
@@ -77,7 +77,7 @@ The way `shared/utils` and `shared/types` auto-imports work and are scanned is i
 -----| formatters
 -------| upper.ts         # Not auto-imported
 ---| types/
------| bar.d.ts           # Auto-imported
+-----| bar.ts             # Auto-imported
 ```
 
 Any other files you create in the `shared/` folder must be manually imported using the `#shared` alias (automatically configured by Nuxt):
@@ -95,4 +95,4 @@ import upper from '#shared/utils/formatters/upper'
 
 This alias ensures consistent imports across your application, regardless of the importing file's location.
 
-:read-more{to="/docs/guide/concepts/auto-imports"}
+:read-more{to="/docs/4.x/guide/concepts/auto-imports"}

package/2.guide/{2.directory-structure → 1.directory-structure}/2.env.md

@@ -2,16 +2,16 @@
 title: ".env"
 description: "A .env file specifies your build/dev-time environment variables."
 head.title: ".env"
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-dotenv
 ---
 
 ::important
-This file should be added to your [`.gitignore`](/docs/guide/directory-structure/gitignore) file to avoid pushing secrets to your repository.
+This file should be added to your [`.gitignore`](/docs/4.x/guide/directory-structure/gitignore) file to avoid pushing secrets to your repository.
 ::
 
 ## Dev, Build and Generate Time
 
-Nuxt CLI has built-in [dotenv](https://github.com/motdotla/dotenv) support in development mode and when running [`nuxt build`](/docs/api/commands/build) and [`nuxt generate`](/docs/api/commands/generate).
+Nuxt CLI has built-in [dotenv](https://github.com/motdotla/dotenv) support in development mode and when running [`nuxt build`](/docs/4.x/api/commands/build) and [`nuxt generate`](/docs/4.x/api/commands/generate).
 
 In addition to any process environment variables, if you have a `.env` file in your project root directory, it will be automatically loaded **at dev, build and generate time**. Any environment variables set there will be accessible within your `nuxt.config` file and modules.
 
@@ -34,7 +34,7 @@ npx nuxt dev --dotenv .env.local
 When updating `.env` in development mode, the Nuxt instance is automatically restarted to apply new values to the `process.env`.
 
 ::important
-In your application code, you should use [Runtime Config](/docs/guide/going-further/runtime-config) instead of plain env variables.
+In your application code, you should use [Runtime Config](/docs/4.x/guide/going-further/runtime-config) instead of plain env variables.
 ::
 
 ## Production
@@ -56,12 +56,12 @@ Since `.env` files are not used in production, you must explicitly set environme
 * Many cloud service providers, such as Vercel, Netlify, and AWS, provide interfaces for setting environment variables via their dashboards, CLI tools or configuration files.
 
 ::important
-`runtimeConfig` [won't pick up environment variables that don't start with `NUXT_` in production] (https://nuxt.com/docs/guide/going-further/runtime-config#environment-variables).
+`runtimeConfig` [won't pick up environment variables that don't start with `NUXT_` in production] (https://nuxt.com/docs/4.x/guide/going-further/runtime-config#environment-variables).
 ::
 
 ## Production Preview
 
-For local production preview purpose, we recommend using [`nuxt preview`](/docs/api/commands/preview) since using this command, the `.env` file will be loaded into `process.env` for convenience. Note that this command requires dependencies to be installed in the package directory.
+For local production preview purpose, we recommend using [`nuxt preview`](/docs/4.x/api/commands/preview) since using this command, the `.env` file will be loaded into `process.env` for convenience. Note that this command requires dependencies to be installed in the package directory.
 
 Or you could pass the environment variables as arguments using the terminal. For example, on Linux or macOS:
 
@@ -71,9 +71,9 @@ DATABASE_HOST=mydatabaseconnectionstring node .output/server/index.mjs
 
 Note that for a purely static site, it is not possible to set runtime configuration config after your project is prerendered.
 
-:read-more{to="/docs/guide/going-further/runtime-config"}
+:read-more{to="/docs/4.x/guide/going-further/runtime-config"}
 
 ::note
 If you want to use environment variables set at build time but do not care about updating these down the line (or only need to update them reactively _within_ your app) then `appConfig` may be a better choice. You can define `appConfig` both within your `nuxt.config` (using environment variables) and also within an `~/app.config.ts` file in your project.
-:read-more{to="/docs/guide/directory-structure/app-config"}
+:read-more{to="/docs/4.x/guide/directory-structure/app-config"}
 ::

package/2.guide/{2.directory-structure → 1.directory-structure}/2.gitignore.md

@@ -2,7 +2,7 @@
 title: ".gitignore"
 description: "A .gitignore file specifies intentionally untracked files that git should ignore."
 head.title: ".gitignore"
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-git
 ---
 
 A `.gitignore` file specifies intentionally untracked files that git should ignore.

package/2.guide/{2.directory-structure → 1.directory-structure}/2.nuxtignore.md

@@ -2,15 +2,16 @@
 title: .nuxtignore
 head.title: '.nuxtignore'
 description: The .nuxtignore file lets Nuxt ignore files in your project’s root directory during the build phase.
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-nuxt
+
 ---
 
-The `.nuxtignore` file tells Nuxt to ignore files in your project’s root directory ([`rootDir`](/docs/api/nuxt-config#rootdir)) during the build phase.
+The `.nuxtignore` file tells Nuxt to ignore files in your project’s root directory ([`rootDir`](/docs/4.x/api/nuxt-config#rootdir)) during the build phase.
 
-It is subject to the same specification as [`.gitignore`](/docs/guide/directory-structure/gitignore) and `.eslintignore` files, in which each line is a glob pattern indicating which files should be ignored.
+It is subject to the same specification as [`.gitignore`](/docs/4.x/guide/directory-structure/gitignore) and `.eslintignore` files, in which each line is a glob pattern indicating which files should be ignored.
 
 ::tip
-You can also configure [`ignoreOptions`](/docs/api/nuxt-config#ignoreoptions), [`ignorePrefix`](/docs/api/nuxt-config#ignoreprefix) and [`ignore`](/docs/api/nuxt-config#ignore) in your `nuxt.config` file.
+You can also configure [`ignoreOptions`](/docs/4.x/api/nuxt-config#ignoreoptions), [`ignorePrefix`](/docs/4.x/api/nuxt-config#ignoreprefix) and [`ignore`](/docs/4.x/api/nuxt-config#ignore) in your `nuxt.config` file.
 ::
 
 ## Usage

package/2.guide/{2.directory-structure → 1.directory-structure}/2.nuxtrc.md

@@ -2,13 +2,13 @@
 title: ".nuxtrc"
 description: "The .nuxtrc file allows you to define nuxt configurations in a flat syntax."
 head.title: ".nuxtrc"
-navigation.icon: i-lucide-file  
+navigation.icon: i-vscode-icons-file-type-nuxt
 ---
 
 The `.nuxtrc` file can be used to configure Nuxt with a flat syntax. It is based on [`unjs/rc9`](https://github.com/unjs/rc9).
 
 ::tip
-For more advanced configurations, use [`nuxt.config`](/docs/guide/directory-structure/nuxt-config).
+For more advanced configurations, use [`nuxt.config`](/docs/4.x/guide/directory-structure/nuxt-config).
 ::
 
 ## Usage
@@ -28,10 +28,10 @@ modules[]=nuxt-security
 If present, the properties in the `nuxt.config` file will overwrite the properties in `.nuxtrc` file.
 
 ::note
-Nuxt automatically adds a `setups` section to track module installation and upgrade state. This is used internally for [module lifecycle hooks](/docs/api/kit/modules#using-lifecycle-hooks-for-module-installation-and-upgrade) and should not be modified manually.
+Nuxt automatically adds a `setups` section to track module installation and upgrade state. This is used internally for [module lifecycle hooks](/docs/4.x/api/kit/modules#using-lifecycle-hooks-for-module-installation-and-upgrade) and should not be modified manually.
 ::
 
-::read-more{to="/docs/api/configuration/nuxt-config"}
+::read-more{to="/docs/4.x/api/configuration/nuxt-config"}
 Discover all the available options in the **Nuxt configuration** documentation.
 ::
 

package/2.guide/{2.directory-structure → 1.directory-structure}/3.nuxt-config.md

@@ -2,7 +2,7 @@
 title: "nuxt.config.ts"
 description: "Nuxt can be easily configured with a single nuxt.config file."
 head.title: "nuxt.config.ts"
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-nuxt
 ---
 
 The `nuxt.config` file extension can either be `.js`, `.ts` or `.mjs`.
@@ -27,8 +27,8 @@ export default defineNuxtConfig({
 })
 ```
 
-::read-more{to="/docs/api/configuration/nuxt-config"}
+::read-more{to="/docs/4.x/api/configuration/nuxt-config"}
 Discover all the available options in the **Nuxt configuration** documentation.
 ::
 
-To ensure your configuration is up to date, Nuxt will make a full restart when detecting changes in the main configuration file, the [`.env`](/docs/guide/directory-structure/env), [`.nuxtignore`](/docs/guide/directory-structure/nuxtignore) and [`.nuxtrc`](/docs/guide/directory-structure/nuxtrc) dotfiles.
+To ensure your configuration is up to date, Nuxt will make a full restart when detecting changes in the main configuration file, the [`.env`](/docs/4.x/guide/directory-structure/env), [`.nuxtignore`](/docs/4.x/guide/directory-structure/nuxtignore) and [`.nuxtrc`](/docs/4.x/guide/directory-structure/nuxtrc) dotfiles.

package/2.guide/{2.directory-structure → 1.directory-structure}/3.package.md

@@ -2,7 +2,7 @@
 title: package.json
 head.title: package.json
 description: The package.json file contains all the dependencies and scripts for your application.
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-npm
 ---
 
 The minimal `package.json` of your Nuxt application should looks like:

package/2.guide/{2.directory-structure → 1.directory-structure}/3.tsconfig.md

@@ -2,10 +2,10 @@
 title: "tsconfig.json"
 description: "Nuxt generates multiple TypeScript configuration files with sensible defaults and your aliases."
 head.title: "tsconfig.json"
-navigation.icon: i-lucide-file
+navigation.icon: i-vscode-icons-file-type-tsconfig
 ---
 
-Nuxt [automatically generates](/docs/guide/concepts/typescript) multiple TypeScript configuration files (`.nuxt/tsconfig.app.json`, `.nuxt/tsconfig.server.json`, `.nuxt/tsconfig.node.json` and `.nuxt/tsconfig.shared.json`) with the resolved aliases you are using in your Nuxt project, as well as with other sensible defaults.
+Nuxt [automatically generates](/docs/4.x/guide/concepts/typescript) multiple TypeScript configuration files (`.nuxt/tsconfig.app.json`, `.nuxt/tsconfig.server.json`, `.nuxt/tsconfig.node.json` and `.nuxt/tsconfig.shared.json`) with the resolved aliases you are using in your Nuxt project, as well as with other sensible defaults.
 
 You can benefit from this by creating a `tsconfig.json` in the root of your project with the following content:
 
@@ -34,5 +34,5 @@ As you need to, you can customize the contents of this file. However, it is reco
 ::
 
 ::note
-If you need to customize your `paths`, this will override the auto-generated path aliases. Instead, we recommend that you add any path aliases you need to the [`alias`](/docs/api/nuxt-config#alias) property within your `nuxt.config`, where they will get picked up and added to the auto-generated `tsconfig`.
+If you need to customize your `paths`, this will override the auto-generated path aliases. Instead, we recommend that you add any path aliases you need to the [`alias`](/docs/4.x/api/nuxt-config#alias) property within your `nuxt.config`, where they will get picked up and added to the auto-generated `tsconfig`.
 ::