Extra add-ons for Nuxt 2 router
Demo: https://codesandbox.io/s/github/nuxt-community/router-extras-module
Looking for a Nuxt 3 alternative? Use the core composable definePageMeta.
Example:
<script setup>
definePageMeta({
path: '/posts',
alias: ['/articles', '/blog']
})
</script>
@nuxtjs/router-extras
dependency to your projectyarn add --dev @nuxtjs/router-extras # or npm install --save-dev @nuxtjs/router-extras
@nuxtjs/router-extras
to the buildModules
section of nuxt.config.js
:warning: If you are using Nuxt < 2.9.0
, use modules
instead.
{
buildModules: [
// Simple usage
'@nuxtjs/router-extras',
// With options
['@nuxtjs/router-extras', { /* module options */ }]
]
}
{
buildModules: [
'@nuxtjs/router-extras'
],
routerExtras: {
/* module options */
}
}
routerNativeAlias
true
Simple aliases will be added as router alias, see vue-router
Simply add a block inside Vue file and define a path in JavaScript or Yaml
If you want more paths for a single page, define them with aliases
Aliases can have their own props
Extras | Support | Description |
---|---|---|
path |
JS & YAML | Change page URL |
alias |
JS & YAML | Add single or multiple aliases to page, Module supports two types of aliases - Simple Alias: These aliases are defined as simple strings. If routerNativeAlias is true, simple aliases will be added as router alias, see vue-router docs - Clone Alias: These aliases are in form of object and they can have their own extras. These aliases will be added as an individual route. They can have their own props and they can have different number of url params |
meta |
JS & YAML | Add Meta information to the page, meta can be used by middlewares |
name |
JS & YAML | Define custom name for route |
props |
JS & YAML | Pass predefined props to page |
beforeEnter |
JS | Define beforeEnter guard for this route, see: Global Before Guards |
caseSensitive |
JS & YAML | Use case sensitive route match (default: false) |
redirect |
JS & YAML | Redirect current page to new location |
namedViews |
JS & YAML | Add named view to the path, see Named Views Support |
There is support for named views in nuxt, but it requires the user to write a lot of boilerplate code in the config. The namedViews
property in the <router>
block allows for a more streamlined configuration
Named views key is a bit different from all other settings. It expects an object with following properties:
currentView
: actual view name for the current component. Defaults to "default"
, to be rendered in plain <nuxt-child />
views
: object, where keys are view names and values are component paths. It supports all expected path resolution (~/
and others)chunkNames
: object, where keys are view names and values are webpack chunks for them. Object structure is expected to be equal to views
- all the same keys must be present.For usage example see example/pages/namedParent.vue
and example/pages/namedParent/namedChild.vue
.
Install Vetur extension and define custom block
<router>
to vetur.grammar.customBlocks
in VSCode settings"vetur.grammar.customBlocks": {
"docs": "md",
"i18n": "json",
"router": "js"
}
> Vetur: Generate grammar from vetur.grammar.customBlocks
in VSCodeyarn install
or npm install
npm run dev
Copyright (c) Nuxt Community