Movatterモバイル変換


[0]ホーム

URL:


Wayback Machine
13 captures
23 Mar 2023 - 17 Jun 2025
MarAPRMay
07
202220232024
success
fail
COLLECTED BY
Organization:Archive Team
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.

The main site for Archive Team is atarchiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.

This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by theWayback Machine, providing a path back to lost websites and work.

Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.

The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.

TIMESTAMPS
loading
The Wayback Machine - http://web.archive.org/web/20230407090913/https://nuxt.com/docs/guide/going-further/custom-routing

👨‍🏫 TheMastering Nuxt 3 course is now completed!

Discover the course

Adding custom routes

In Nuxt 3, your routing is defined by the structure of your files inside thepages directory. However, since it usesvue-router under the hood, Nuxt offers you several ways to add custom routes in your project.

Using router config

Usingrouter options, you can optionally override or extend your routes using a function that accepts the scanned routes and returns customized routes.

If it returnsnull orundefined, Nuxt will fall back to the default routes (useful to modify input array).

app/router.options.ts
importtype {RouterConfig }from'@nuxt/schema'
// https://router.vuejs.org/api/interfaces/routeroptions.html
exportdefault <RouterConfig>{
routes: (_routes)=> [
{
name:'home',
path:'/',
component: ()=>import('~/pages/home.vue').then(r=>r.default||r)
}
],
}

Nuxt will not augment any new routes you return from theroutes function with metadata defined indefinePageMeta of the component you provide. If you want that to happen, you should use thepages:extend hook which iscalled at build-time.

Using thepages:extend hook

You can add, change or remove pages from the scanned routes with thepages:extend nuxt hook. For example, to prevent creating routes for any.ts files:

nuxt.config.ts
exportdefaultdefineNuxtConfig({
hooks: {
'pages:extend' (pages) {
// add a route
pages.push({
name:'profile',
path:'/profile',
file:'~/extra-pages/profile.vue'
})
// remove routes
functionremovePagesMatching (pattern:RegExp,pages:NuxtPage[]= []) {
constpagesToRemove= []
for (constpageofpages) {
if (pattern.test(page.file)) {
pagesToRemove.push(page)
}else {
removePagesMatching(pattern,page.children)
}
}
for (constpageofpagesToRemove) {
pages.splice(pages.indexOf(page),1)
}
}
removePagesMatching(/\.ts$/,pages)
}
}
})

Using a module

If you plan to add a whole set of pages related with a specific functionality, you might want to use aNuxt module.

TheNuxt kit provides a few waysto add routes:

  • extendPages (callback: pages => void)
  • extendRouteRules (route: string, rule: NitroRouteConfig, options: ExtendRouteRulesOptions)

Router Options

It is possible to customizevue-router options.

Usingapp/router.options

It is possible to customizevue-router options.

This is the recommended way to specify router options.

app/router.options.ts
importtype {RouterConfig }from'@nuxt/schema'
// https://router.vuejs.org/api/interfaces/routeroptions.html
exportdefault <RouterConfig>{
}

Usingnuxt.config

Note: Only JSON serializable options are configurable:

  • linkActiveClass
  • linkExactActiveClass
  • end
  • sensitive
  • strict
  • hashMode
nuxt.config
exportdefaultdefineNuxtConfig({
router: {
// https://router.vuejs.org/api/interfaces/routeroptions.html
options: {}
}
})

Hash Mode (SPA)

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, theURL is never sent to the server andSSR is not supported.

nuxt.config.ts
exportdefaultdefineNuxtConfig({
ssr:false,
router: {
options: {
hashMode:true
}
}
})

Custom History (advanced)

You can optionally override history mode using a function that accepts the base URL and returns the history mode. If it returnsnull orundefined, Nuxt will fallback to the default history.

app/router.options.ts
importtype {RouterConfig }from'@nuxt/schema'
import {createMemoryHistory }from'vue-router'
// https://router.vuejs.org/api/interfaces/routeroptions.html
exportdefault <RouterConfig>{
history:base=>process.client?createMemoryHistory(base):null/* default */
}

[8]ページ先頭

©2009-2025 Movatter.jp