chore: update examples to ^3.0.0-rc.10 and use global `defineNuxtCo…

…nfig` (#7515)

docs/content/1.getting-started/4.assets.md

@@ -70,8 +70,6 @@ In your `nuxt.config`
 ::code-group
 
 ```ts [SCSS]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   vite: {
     css: {
@@ -86,8 +84,6 @@ export default defineNuxtConfig({
 ```
 
 ```ts [SASS]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   vite: {
     css: {

docs/content/1.getting-started/9.testing.md

@@ -148,7 +148,6 @@ To test the modules we create, we could set up some Nuxt apps as fixtures and te
 
 ```ts
 // nuxt.config.js
-import { defineNuxtConfig } from 'nuxt'
 import MyModule from '../../src'
 
 export default defineNuxtConfig({

docs/content/2.guide/1.concepts/7.esm.md

@@ -117,8 +117,6 @@ If you encounter these errors, the issue is almost certainly with the upstream l
 In the meantime, you can tell Nuxt not to try to import these libraries by adding them to `build.transpile`:
 
 ```js
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   build: {
     transpile: ['sample-library']
@@ -133,8 +131,6 @@ You may find that you _also_ need to add other packages that are being imported
 In some cases, you may also need to manually alias the library to the CJS version, for example:
 
 ```js
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   alias: {
     'sample-library': 'sample-library/dist/sample-library.cjs.js'

docs/content/2.guide/2.directory-structure/1.components.md

@@ -70,7 +70,6 @@ If you are using `resolveComponent` to handle dynamic components, make sure not
 Alternatively, though not recommended, you can register all your components globally, which will create async chunks for all your components and make them available throughout your application.
 
 ```diff
-  import { defineNuxtConfig } from 'nuxt'
 
   export default defineNuxtConfig({
     components: {
@@ -187,7 +186,7 @@ Make sure not to _nest_ `<ClientOnly>` components or other client-only component
 If a component is meant to be rendered only client-side, you can add the `.client` suffix to your component.
 
 ```bash
-| components/ 
+| components/
 --| Comments.client.vue
 ```
 
@@ -209,14 +208,14 @@ This feature only works with Nuxt auto-imports. Explicitly importing these compo
 `.server` components are fallback components of `.client` components.
 
 ```bash
-| components/ 
+| components/
 --| Comments.client.vue
 --| Comments.server.vue
 ```
 
 ```html{}[pages/example.vue]
 <template>
-  <div> 
+  <div>
     <!-- this component will render Comments.server server-side then Comments.client once mounted in client-side -->
     <Comments />
   </div>

docs/content/2.guide/2.directory-structure/1.content.md

@@ -42,8 +42,6 @@ Install the `@nuxt/content` module in your project:
 Then, add `@nuxt/content` to the `modules` section of `nuxt.config.ts`:
 
 ```ts [nuxt.config.ts]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   modules: [
     '@nuxt/content'

docs/content/2.guide/2.directory-structure/1.pages.md

@@ -407,8 +407,6 @@ export default defineNuxtConfig({
 You can enable hash history in SPA mode. In this mode, router uses a hash character (#) before the actual URL that is internally passed. When enabled, the **URL is never sent to the server** and **SSR is not supported**.
 
 ```ts [nuxt.config.ts]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   ssr: false,
   router: {

docs/content/2.guide/2.directory-structure/1.server.md

@@ -177,8 +177,6 @@ This is an advanced option. Custom config can affect production deployments, as
 ::
 
 ```ts [nuxt.config.ts]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   // https://nitro.unjs.io/config
   nitro: {}
@@ -240,8 +238,6 @@ Nitro provides a cross-platform [storage layer](https://nitro.unjs.io/guide/intr
 #### Example: Using Redis
 
 ```ts [nuxt.config.ts]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   nitro: {
     storage: {

docs/content/2.guide/2.directory-structure/3.nuxt.config.md

@@ -9,7 +9,20 @@ head.title: Nuxt Configuration file
 Nuxt can be easily configured with a single `nuxt.config` file, which can have either a `.js`, `.ts` or `.mjs` extension.
 
 ```ts
-import { defineNuxtConfig } from 'nuxt'
+export default defineNuxtConfig({
+  // My Nuxt config
+})
+```
+
+
+::alert
+`defineNuxtConfig` helper is globally available without import.
+::
+
+You can explicitily import `defineNuxtConfig` from `nuxt/config` if you prefer:
+
+```js
+import { defineNuxtConfig } from 'nuxt/config'
 
 export default defineNuxtConfig({
   // My Nuxt config

docs/content/bridge/1.overview.md

@@ -179,7 +179,6 @@ Add the folder `.output` to the `.gitignore` file.
 
 ```ts [nuxt.config.js|ts]
 import { defineNuxtConfig } from '@nuxt/bridge'
-
 export default defineNuxtConfig({
   bridge: false // Temporarily disable bridge integration
 })
@@ -222,7 +221,6 @@ You will also need to enable this feature explicitly in your `nuxt.config`:
 
 ```js
 import { defineNuxtConfig } from '@nuxt/bridge'
-
 export default defineNuxtConfig({
   bridge: {
     meta: true
@@ -243,7 +241,6 @@ You can check [bridge/src/module.ts](https://github.com/nuxt/bridge/blob/main/sr
 
 ```ts [nuxt.config.js|ts]
 import { defineNuxtConfig } from '@nuxt/bridge'
-
 export default defineNuxtConfig({
   bridge: {
 

docs/content/migration/2.configuration.md

@@ -26,8 +26,6 @@ Nuxt configuration will be loaded using [`unjs/jiti`](https://github.com/unjs/ji
    ```
 
    ```ts [Nuxt 3]
-   import { defineNuxtConfig } from 'nuxt'
-
    export default defineNuxtConfig({
      // ...
    })
@@ -50,8 +48,6 @@ Nuxt configuration will be loaded using [`unjs/jiti`](https://github.com/unjs/ji
    ```
 
    ```ts [Nuxt 3]
-   import { defineNuxtConfig } from 'nuxt'
-
    export default defineNuxtConfig({
      hooks: {
        'pages:extend' (routes) {

docs/content/migration/8.runtime-config.md

@@ -21,8 +21,6 @@ When referencing these variables within your components, you will have to use th
 ::code-group
 
 ```ts [nuxt.config.ts]
-import { defineNuxtConfig } from 'nuxt'
-
 export default defineNuxtConfig({
   runtimeConfig: {
     // Private config that is only available on the server
@@ -38,7 +36,7 @@ export default defineNuxtConfig({
 ```vue [pages/index.vue]
 <script setup>
   const config = useRuntimeConfig()
-  
+
   // instead of process.env you will now access config.public.apiBase
   console.log(config.public.apiBase)
 </script>