@nuxt/docs-nightly 4.1.3-29313386.edc02e27 → 4.1.3-29316215.910d159d

package/7.migration/6.pages-and-layouts.md

@@ -13,9 +13,9 @@ If you don't have an `app.vue` file in your source directory, Nuxt will use its
 
 This file is a great place to put any custom code that needs to be run once when your app starts up, as well as any components that are present on every page of your app. For example, if you only have one layout, you can move this to `app.vue` instead.
 
-:read-more{to="/docs/guide/directory-structure/app"}
+:read-more{to="/docs/4.x/guide/directory-structure/app"}
 
-:link-example{to="/docs/examples/hello-world"}
+:link-example{to="/docs/4.x/examples/hello-world"}
 
 ### Migration
 
@@ -84,13 +84,13 @@ In Nuxt 2, you will have defined any nested routes (with parent and child compon
 
 If you were passing a custom page key or keep-alive props to `<Nuxt>`, you will now use `definePageMeta` to set these options.
 
-:read-more{to="/docs/guide/directory-structure/app/pages#special-metadata"}
+:read-more{to="/docs/4.x/guide/directory-structure/app/pages#special-metadata"}
 
 ### Page and Layout Transitions
 
 If you have been defining transitions for your page or layout directly in your component options, you will now need to use `definePageMeta` to set the transition. Since Vue 3, [-enter and -leave CSS classes have been renamed](https://v3-migration.vuejs.org/breaking-changes/transition.html). The `style` prop from `<Nuxt>` no longer applies to transition when used on `<slot>`, so move the styles to your `-active` class.
 
-:read-more{to="/docs/getting-started/transitions"}
+:read-more{to="/docs/4.x/getting-started/transitions"}
 
 ### Migration
 
@@ -145,13 +145,17 @@ If you have been defining transitions for your page or layout directly in your c
 ```vue [Nuxt 2]
 <template>
   <div>
-    <NuxtChild keep-alive :keep-alive-props="{ exclude: ['modal'] }" :nuxt-child-key="$route.slug" />
+    <NuxtChild
+      keep-alive
+      :keep-alive-props="{ exclude: ['modal'] }"
+      :nuxt-child-key="$route.slug"
+    />
   </div>
 </template>
 
 <script>
 export default {
-  transition: 'page' // or { name: 'page' }
+  transition: 'page', // or { name: 'page' }
 }
 </script>
 ```
@@ -172,7 +176,7 @@ definePageMeta({
     name: 'page',
   },
   keepalive: {
-    exclude: ['modal']
+    exclude: ['modal'],
   },
 })
 </script>
@@ -186,7 +190,7 @@ Most of the syntax and functionality are the same for the global [NuxtLink](/doc
 
 `<NuxtLink>` is now a drop-in replacement for _all_ links, even external ones. You can read more about it, and how to extend it to provide your own link component.
 
-:read-more{to="/docs/api/components/nuxt-link"}
+:read-more{to="/docs/4.x/api/components/nuxt-link"}
 
 ## Programmatic Navigation
 
@@ -202,29 +206,29 @@ Make sure to always `await` on [`navigateTo`](/docs/4.x/api/utils/navigate-to) o
 <script>
 export default {
   methods: {
-    navigate(){
+    navigate () {
       this.$router.push({
         path: '/search',
         query: {
           name: 'first name',
-          type: '1'
-        }
+          type: '1',
+        },
       })
-    }
-  }
+    },
+  },
 }
 </script>
 ```
 
 ```vue [Nuxt 3]
 <script setup lang="ts">
-function navigate(){
+function navigate () {
   return navigateTo({
     path: '/search',
     query: {
       name: 'first name',
-      type: '1'
-    }
+      type: '1',
+    },
   })
 }
 </script>

package/7.migration/7.component-options.md

@@ -30,14 +30,14 @@ In Nuxt 2, you'd fetch your data in your component using a syntax similar to:
 
 ```ts
 export default {
-  async asyncData({ params, $http }) {
+  async asyncData ({ params, $http }) {
     const post = await $http.$get(`https://api.nuxtjs.dev/posts/${params.id}`)
     return { post }
   },
   // or alternatively
   fetch () {
     this.post = await $http.$get(`https://api.nuxtjs.dev/posts/${params.id}`)
-  }
+  },
 }
 ```
 
@@ -48,7 +48,7 @@ With Nuxt 3, you can perform this data fetching using composables in your `setup
 ```vue
 <script setup lang="ts">
 // Define params wherever, through `defineProps()`, `useRoute()`, etc.
-const { data: post, refresh } = await useAsyncData('post', () => $fetch(`https://api.nuxtjs.dev/posts/${params.id}`) )
+const { data: post, refresh } = await useAsyncData('post', () => $fetch(`https://api.nuxtjs.dev/posts/${params.id}`))
 // Or instead - useFetch is a convenience wrapper around useAsyncData when you're just performing a simple fetch
 const { data: post, refresh } = await useFetch(`https://api.nuxtjs.dev/posts/${params.id}`)
 </script>
@@ -67,7 +67,7 @@ Despite the names, [`useFetch`](/docs/4.x/api/composables/use-fetch) is not a di
 
 ## `head`
 
-:read-more{to="/docs/migration/meta"}
+:read-more{to="/docs/4.x/migration/meta"}
 
 ## `key`
 
@@ -91,7 +91,7 @@ You can now define a key within the [`definePageMeta`](/docs/4.x/api/utils/defin
 
 ## `layout`
 
-:read-more{to="/docs/migration/pages-and-layouts"}
+:read-more{to="/docs/4.x/migration/pages-and-layouts"}
 
 ## `loading`
 
@@ -99,7 +99,7 @@ This feature is not yet supported in Nuxt 3.
 
 ## `middleware`
 
-:read-more{to="/docs/migration/plugins-and-middleware"}
+:read-more{to="/docs/4.x/migration/plugins-and-middleware"}
 
 ## `scrollToTop`
 
@@ -120,7 +120,7 @@ Similar to `key`, specify it within the [`definePageMeta`](/docs/4.x/api/utils/d
 
 ## `transition`
 
-:read-more{to="/docs/getting-started/transitions"}
+:read-more{to="/docs/4.x/getting-started/transitions"}
 
 ## `validate`
 

package/7.migration/8.runtime-config.md

@@ -9,7 +9,7 @@ When referencing these variables within your components, you will have to use th
 
 In the `server/` portion of your app, you can use [`useRuntimeConfig`](/docs/4.x/api/composables/use-runtime-config) without any import.
 
-:read-more{to="/docs/guide/going-further/runtime-config"}
+:read-more{to="/docs/4.x/guide/going-further/runtime-config"}
 
 ## Migration
 
@@ -25,9 +25,9 @@ export default defineNuxtConfig({
     apiSecret: '123',
     // Config within public will be also exposed to the client
     public: {
-      apiBase: '/api'
-    }
-  }
+      apiBase: '/api',
+    },
+  },
 })
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "4.1.3-29313386.edc02e27",
+  "version": "4.1.3-29316215.910d159d",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",