` into `app.vue` file.\r\n5) Add some page in `pages` folder\r\n6) See type errors when using `$route` in the template or global `useRoute()` function in composition API.\r\n\r\n### Describe the bug\r\n\r\nThere are type errors when just using Nuxt 3 pages router out of the box.\r\n\r\n### Additional context\r\n\r\n**package.json**\r\n\r\n```\r\n{\r\n \"name\": \"my-new-nuxt-app\",\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/devtools\": \"^0.5.5\",\r\n \"@types/node\": \"^18.16.18\",\r\n \"nuxt\": \"^3.6.1\"\r\n },\r\n \"overrides\": {\r\n \"vue\": \"latest\"\r\n }\r\n}\r\n```\r\n\r\n**app.vue**\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtPage />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n**pages/[code].vue**\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cp>{{ $route.params.code }}\u003C/p>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\n const route = useRoute()\r\n console.log('code:', route.params.code)\r\n\u003C/script>\r\n```\r\n\r\n**nuxt.config.ts**\r\n\r\n```\r\n// https://nuxt.com/docs/api/configuration/nuxt-config\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n pages: true,\r\n})\r\n```\r\n\r\nVS Code\r\nNode v16.14.2\r\nNPM 8.5.0\r\n\r\n### Logs\r\n\r\n_No response_",[3003,3004,3005],{"name":2955,"color":2956},{"name":2933,"color":2934},{"name":2990,"color":2991},21859,"Pages route type issue","2023-06-29T10:04:02Z","https://github.com/nuxt/nuxt/issues/21859",0.6829648,{"description":3012,"labels":3013,"number":3019,"owner":2939,"repository":2939,"state":2961,"title":3020,"updated_at":3021,"url":3022,"score":3023},"### Describe the feature\n\nHi, \r\n\r\nI'm trying to migrate Nuxt2 to Nuxt3, we had implemented alias management by API which is then implemented in extendRoutes (n2).\r\n\r\nIn Nuxt3 the aliases are to be put directly in the page files with `definePageMeta` but this restricts the use.\r\n\r\nMethod to Reproduce :\r\n\r\n- Use the `page:extend` hook (in nuxt.config) or use Module like [Doc](https://v3.nuxtjs.org/examples/server/routes)\r\n- Implement aliases dynamically\r\n\r\n```js\r\nexport default defineNuxtModule({\r\n setup () {\r\n extendPages(async (routes) => {\r\n routes.forEach((route) => {\r\n routes.alias = ['/a', '/b']\r\n });\r\n })\r\n })\r\n }\r\n})\r\n```\r\n- Today this way doesn't work.\r\n\r\n\r\nThis is due to : `packages/nuxt/src/pages/utils.ts` (alias property)\r\n\r\n```js\r\nexport function normalizeRoutes (routes: NuxtPage[], metaImports: Set\u003Cstring> = new Set()): { imports: Set\u003Cstring>, routes: string } {\r\n return {\r\n imports: metaImports,\r\n routes: genArrayFromRaw(routes.map((route) => {\r\n const file = normalize(route.file)\r\n const metaImportName = genSafeVariableName(file) + 'Meta'\r\n metaImports.add(genImport(`${file}?macro=true`, [{ name: 'meta', as: metaImportName }]))\r\n return {\r\n ...Object.fromEntries(Object.entries(route).map(([key, value]) => [key, JSON.stringify(value)])),\r\n children: route.children ? normalizeRoutes(route.children, metaImports).routes : [],\r\n meta: route.meta ? `{...(${metaImportName} || {}), ...${JSON.stringify(route.meta)}}` : metaImportName,\r\n alias: `${metaImportName}?.alias || []`,\r\n component: genDynamicImport(file, { interopDefault: true })\r\n }\r\n }))\r\n }\r\n}\r\n```\r\n\r\nI have already made the fix on my project\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3014,3015,3018],{"name":2949,"color":2950},{"name":3016,"color":3017},"discussion","538de2",{"name":2955,"color":2956},14750,"Feat : Router Alias capability extended (Dynamically)","2023-01-19T17:39:46Z","https://github.com/nuxt/nuxt/issues/14750",0.68897015,{"labels":3025,"number":3028,"owner":2939,"repository":2939,"state":2961,"title":3029,"updated_at":3030,"url":3031,"score":3032},[3026,3027],{"name":2955,"color":2956},{"name":2933,"color":2934},13600,"Wrong typing on RouterOptions","2023-01-19T17:00:21Z","https://github.com/nuxt/nuxt/issues/13600",0.689443,{"description":3034,"labels":3035,"number":3038,"owner":2939,"repository":2939,"state":2961,"title":3039,"updated_at":3040,"url":3041,"score":3042},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `2.0.0-27860563.409fe2b`\r\n- Package Manager: `pnpm@7.8.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://github.com/nuxt/framework/blob/main/packages/nuxt/src/pages/module.ts\n\n### Describe the bug\n\nHi :wave: , I'm not sure if this is a bug or if this should be converted into a discussion.\r\n\r\n Currently i'm using the `router.options.ts` on one project to define my routes. I've tried to use `@nuxtjs/i18n` for lang translation but i've been struggling to make it work. \r\n\r\n i18n use `page:extends` to prefix routes. However, `router.options.ts` routes are being added after the `page:extend` hook as you can see [here ](https://github.com/nuxt/framework/blob/9de94c21cf7fa7008c75f859e0299e3f1c0b445c/packages/nuxt/src/pages/module.ts#L187-L211) .\r\n We also can't add it through the nuxt config due to the type `RouterConfigSerializable`.\r\n\r\n Can we maybe merge the routes generated from the `page` dir and those provided by `router.options.ts` ?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3036,3037],{"name":2955,"color":2956},{"name":2933,"color":2934},12335,"app/router.options pages are not in `page:extend` hook","2023-01-30T11:57:17Z","https://github.com/nuxt/nuxt/issues/12335",0.6914127,{"description":3044,"labels":3045,"number":3048,"owner":2939,"repository":2939,"state":2961,"title":3049,"updated_at":3050,"url":3051,"score":3052},"### Describe the feature\n\n`RouteNamedMap` from `#vue-router` have now all locale suffixes, and type checking not working in `localePath`. [Nuxt Typed Router](https://nuxt-typed-router.vercel.app/) already has i18n support.\r\n\r\n\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3046,3047],{"name":2955,"color":2956},{"name":2933,"color":2934},21048,"[experimental.typedPages] Support i18n","2024-07-15T13:07:41Z","https://github.com/nuxt/nuxt/issues/21048",0.6917346,["Reactive",3054],{},["Set"],["ShallowReactive",3057],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGn5JEVychrN3vH1_bQ9Gs_yftdN1PT4ktQUNgacUnTs":-1},"/nuxt/nuxt/27414"]