From fdd4bddf358a9dccb73ffffd4c3a9a402e1fa88d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=B1=9F=E9=BA=BB=E5=A6=9E?= Date: Thu, 9 Mar 2023 23:25:47 +0800 Subject: [PATCH] docs: update various nitro links (#19562) --- docs/2.guide/1.concepts/3.rendering.md | 2 +- docs/2.guide/2.directory-structure/1.server.md | 4 ++-- packages/schema/src/config/nitro.ts | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/2.guide/1.concepts/3.rendering.md b/docs/2.guide/1.concepts/3.rendering.md index e0a6a255d1..68158d9bdc 100644 --- a/docs/2.guide/1.concepts/3.rendering.md +++ b/docs/2.guide/1.concepts/3.rendering.md @@ -87,7 +87,7 @@ Nitro is the new [server engine](/docs/guide/concepts/server-engine) that powers Previously every route/page of a Nuxt application and server must use the same rendering mode, client-side or universal. But in various cases, some pages could be generated at build time, while others should be client-side rendered. For example, think of a content website with an admin section. Every content page should be primarily static and generated once, but the admin section requires registration and behaves more like a dynamic application. -Nuxt 3 starting from rc.12 comes with the public beta for route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/introduction/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently Netlify and Vercel are supported). +Nuxt 3 starting from rc.12 comes with the public beta for route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently Netlify and Vercel are supported). - `redirect` - Define server-side redirects. - `ssr` - Disables server-side rendering for sections of your app and make them SPA-only with `ssr: false` diff --git a/docs/2.guide/2.directory-structure/1.server.md b/docs/2.guide/2.directory-structure/1.server.md index 3b3249531a..d53346e237 100644 --- a/docs/2.guide/2.directory-structure/1.server.md +++ b/docs/2.guide/2.directory-structure/1.server.md @@ -13,7 +13,7 @@ Each file should export a default function defined with `defineEventHandler()`. The handler can directly return JSON data, a `Promise` or use `event.node.res.end()` to send response. -::ReadMore{link="https://nitro.unjs.io/guide/introduction/routing" title="Nitro Route Handling Docs"} +::ReadMore{link="https://nitro.unjs.io/guide/routing" title="Nitro Route Handling Docs"} :: ## Example @@ -288,7 +288,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.unjs.io/guide/introduction/storage). In order to configure additional storage mount points, you can use `nitro.storage`. +Nitro provides a cross-platform [storage layer](https://nitro.unjs.io/guide/storage). In order to configure additional storage mount points, you can use `nitro.storage`. #### Example: Using Redis diff --git a/packages/schema/src/config/nitro.ts b/packages/schema/src/config/nitro.ts index 9935128c2f..5e1a79cb76 100644 --- a/packages/schema/src/config/nitro.ts +++ b/packages/schema/src/config/nitro.ts @@ -56,7 +56,7 @@ export default defineUntypedSchema({ /** * Nitro development-only server handlers. * - * @see https://nitro.unjs.io/guide/introduction/routing + * @see https://nitro.unjs.io/guide/routing * * @type {typeof import('nitropack')['NitroDevEventHandler'][]} */