@nuxt/docs-nightly 5.0.0-29745651.30ee274e → 5.0.0-29746777.c24c1069
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -43,7 +43,10 @@ When running [`nuxt build`](/docs/4.x/api/commands/build), the home page will be
|
|
|
43
43
|
## Notes
|
|
44
44
|
|
|
45
45
|
- A rule defined in `~/pages/foo/bar.vue` will be applied to `/foo/bar` requests.
|
|
46
|
-
- A rule in `~/pages/foo/[id].vue` will be applied to `/foo
|
|
46
|
+
- A rule in `~/pages/foo/[id].vue` will be applied to `/foo/*` requests.
|
|
47
|
+
- A rule in a page with a finite set of alternatives, such as a custom `path` of `/:locale(en|fr)/about`, will generate one rule per alternative (`/en/about` and `/fr/about`).
|
|
48
|
+
|
|
49
|
+
If a page path cannot be converted to an equivalent route rule pattern (for example, a param with a regular expression like `/:id(\d+)`, a partial segment like `/prefix-:id`, or a repeatable param like `/:slug+`), the rules for that page are **not** applied and Nuxt warns during build. In that case, define the rules explicitly in `nitro.routeRules` in your `nuxt.config`.
|
|
47
50
|
|
|
48
51
|
For more control, such as if you are using a custom `path` or `alias` set in the page's [`definePageMeta`](/docs/4.x/api/utils/define-page-meta), you should set `routeRules` directly within your `nuxt.config`.
|
|
49
52
|
|