@nuxt/docs-nightly 5.0.0-29560209.2c61a3c1 → 5.0.0-29560959.2cd7cfc5

package/1.getting-started/04.views.md

@@ -151,7 +151,9 @@ The callback function of the `render:html` hook allows you to mutate the HTML be
 <!-- TODO: figure out how to use twoslash to inject types for a different context -->
 
 ```ts [server/plugins/extend-html.ts]
-export default defineNitroPlugin((nitroApp) => {
+import { definePlugin } from 'nitro'
+
+export default definePlugin((nitroApp) => {
   nitroApp.hooks.hook('render:html', (html, { event }) => {
     // This will be an object representation of the html template.
     console.log(html)

package/1.getting-started/06.styling.md

@@ -160,7 +160,9 @@ Create a plugin in `~~/server/plugins/my-plugin.ts` like this:
 <!-- TODO: figure out how to use twoslash to inject types for a different context -->
 
 ```ts [server/plugins/my-plugin.ts]
-export default defineNitroPlugin((nitro) => {
+import { definePlugin } from 'nitro'
+
+export default definePlugin((nitro) => {
   nitro.hooks.hook('render:html', (html) => {
     html.head.push('<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/animate.css/4.1.1/animate.min.css">')
   })

package/1.getting-started/18.upgrade.md

@@ -234,7 +234,7 @@ The `nitropack` package has been renamed to `nitro`. All import paths have chang
 |---|---|
 | `nitropack` | `nitro` |
 | `nitropack/types` | `nitro/types` |
-| `nitropack/runtime` | `nitro/runtime` |
+| `nitropack/runtime` | `nitro` |
 | `h3` (for server utilities) | `nitro/h3` |
 
 Auto-imports within server routes (`defineEventHandler`, `getQuery`, `readBody`, `useRuntimeConfig`, etc.) continue to work without changes.
@@ -345,7 +345,7 @@ If you define redirect route rules, the property name has changed:
 
 #### For Module Authors: Additional Changes
 
-- **Nitro plugin imports**: Use `import { defineNitroPlugin } from 'nitro/runtime'` for explicit imports (auto-imports still work).
+- **Nitro plugin imports**: Use `import { definePlugin } from 'nitro'` for explicit imports (auto-imports still work).
 - **Runtime hooks**: `nitroApp.hooks.hook('beforeResponse', ...)` and `nitroApp.hooks.hook('afterResponse', ...)` have been replaced by `nitroApp.hooks.hook('response', ...)`.
 - **`getRouteRules()` from `nitro/app`**: On the server, the Nitro helper changed from `getRouteRules(event)` to `getRouteRules(method, pathname)`, which returns `{ routeRules }`.
 

package/2.directory-structure/1.server.md

@@ -94,7 +94,9 @@ Nuxt will automatically read any files in the `~~/server/plugins` directory and
 **Example:**
 
 ```ts [server/plugins/nitroPlugin.ts]
-export default defineNitroPlugin((nitroApp) => {
+import { definePlugin } from 'nitro'
+
+export default definePlugin((nitroApp) => {
   console.log('Nitro plugin', nitroApp)
 })
 ```
@@ -526,9 +528,10 @@ Alternatively, you can create a storage mount point using a server plugin and ru
 
 ::code-group
 ```ts [server/plugins/storage.ts]
+import { definePlugin } from 'nitro'
 import redisDriver from 'unstorage/drivers/redis'
 
-export default defineNitroPlugin(() => {
+export default definePlugin(() => {
   const storage = useStorage()
 
   // Dynamically pass in credentials from runtime configuration, or other sources

package/3.guide/6.going-further/2.hooks.md

@@ -58,7 +58,9 @@ Explore all available App hooks.
 These hooks are available for [server plugins](/docs/4.x/directory-structure/server#server-plugins) to hook into Nitro's runtime behavior.
 
 ```ts [~~/server/plugins/test.ts]
-export default defineNitroPlugin((nitroApp) => {
+import { definePlugin } from 'nitro'
+
+export default definePlugin((nitroApp) => {
   nitroApp.hooks.hook('render:html', (html, { event }) => {
     console.log('render:html', html)
     html.bodyAppend.push('<hr>Appended by custom plugin')

package/4.api/5.kit/11.nitro.md

@@ -200,7 +200,7 @@ You can read more about Nitro plugins in the [Nitro documentation](https://nitro
 ::
 
 ::warning
-It is necessary to explicitly import `defineNitroPlugin` from `nitro/runtime` within your plugin file. The same requirement applies to utilities such as `useRuntimeConfig`.
+It is necessary to explicitly import `definePlugin` from `` within your plugin file. The same requirement applies to utilities such as `useRuntimeConfig`.
 ::
 
 ### Usage
@@ -244,9 +244,9 @@ export default defineNuxtModule({
 ```
 
 ```ts [runtime/plugin.ts]
-import { defineNitroPlugin } from 'nitro/runtime'
+import { definePlugin } from 'nitro'
 
-export default defineNitroPlugin((nitroApp) => {
+export default definePlugin((nitroApp) => {
   nitroApp.hooks.hook('request', (event) => {
     console.log('on request', event.req.url)
   })

package/4.api/6.nuxt-config.md

@@ -1495,7 +1495,7 @@ Modules to generate deep aliases for within `compilerOptions.paths`. This does n
 ```json
 [
   "nitro/types",
-  "nitro/runtime",
+  "nitro/runtime-config",
   "nitro",
   "defu",
   "h3",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nuxt/docs-nightly",
-  "version": "5.0.0-29560209.2c61a3c1",
+  "version": "5.0.0-29560959.2cd7cfc5",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/nuxt/nuxt.git",