\r\n \u003C/NuxtLayout>\r\n\u003C/template>\r\n```\r\nChange the pages directory to something else in `nuxt.config.ts`.\r\n```ts\r\n// https://nuxt.com/docs/api/configuration/nuxt-config\r\nexport default defineNuxtConfig({\r\n dir: {\r\n pages: \"routes\"\r\n }\r\n});\r\n```\r\nMake sure to not have anything in the pages directory.\n\n### Describe the bug\n\nNuxt throws info message `Create a Vue component in the pages/ directory to enable \u003CNuxtPage>` instead of `Create a Vue component in the (pages dir)/ directory to enable \u003CNuxtPage>`.\n\n### Additional context\n\nLiterally no one cares, but I get annoyed by anything.\n\n### Logs\n\n_No response_",[2883,2886],{"name":2884,"color":2885},"3.x","29bc7f",{"name":2887,"color":2888},"pending triage","E99695",20064,"closed","\u003CNuxtPage> info message does not take custom pages dir into account","2023-04-04T13:18:31Z","https://github.com/nuxt/nuxt/issues/20064",0.6040814,{"description":2896,"labels":2897,"number":2900,"owner":2874,"repository":2874,"state":2890,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: modules\r\n- Runtime Modules: ./modules/test-module\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-hcx5za\n\n### Describe the bug\n\nIf `pages/` directory is not created or is empty and all of the pages are defined using `extendPages` in module, it throws warning:\r\n\r\n`Create a Vue component in the pages/ directory to enable \u003CNuxtPage>`\r\n\r\nand shows blank page.\r\n\r\nIf you create e.g. `pages/test.vue`, warning goes away and displays the intended page.\n\n### Additional context\n\nAlso this warning goes away, if I create `app/router.options.ts` file.\n\n### Logs\n\n_No response_",[2898,2899],{"name":2884,"color":2885},{"name":2887,"color":2888},20801,"\u003CNuxtPage> info message does not look up for module pages","2023-05-15T12:47:31Z","https://github.com/nuxt/nuxt/issues/20801",0.6102908,{"description":2906,"labels":2907,"number":2910,"owner":2874,"repository":2874,"state":2890,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.3.1`\r\n- Nitro Version: `2.3.1`\r\n- Package Manager: `pnpm@7.8.0`\r\n- Builder: `vite`\r\n- User Config: `modules`, `quasar`, `vite`, `runtimeConfig`, `typescript`, `hooks`\r\n- Runtime Modules: `nuxt-quasar-ui@1.0.4`, `@vueuse/nuxt@9.13.0`\r\n- Build Modules: `-`\n\n### Reproduction\n\nOccurrence in documentation: https://nuxt.com/docs/guide/going-further/custom-routing#using-the-pagesextend-hook\r\n\r\nCorresponding type definition: https://github.com/nuxt/nuxt/blob/main/packages/schema/src/types/hooks.ts#L22-L30\n\n### Describe the bug\n\nThe documentation adds a route using a `component`. While this should work for directly adding it to the router (`RouteRecordRaw[]`), it does not work for adding routes within the `pages:extend` hook and in my testing lead to errors.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2908,2909],{"name":2884,"color":2885},{"name":2887,"color":2888},19940,"Defining a route (NuxtPage) does not permit `component` property though documentation uses it","2023-03-28T10:25:04Z","https://github.com/nuxt/nuxt/issues/19940",0.63364285,{"description":2916,"labels":2917,"number":2926,"owner":2874,"repository":2874,"state":2890,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n1. Open this [StackBlitz](https://stackblitz.com/edit/https-github-comnuxtframeworkissues8177)\r\n2. See that no page is shown\r\n3. Expected: Showing the content of `Test.vue`\r\n4. Actual: Showing `\u003CNuxtWelcome>`\r\n\r\n### Describe the bug\r\n\r\nUsing `app/router.options.ts` without a `pages` folder (even with `pages: true` in `nuxt.config.ts`) does utilize the custom router.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2918,2919,2922,2923],{"name":2868,"color":2869},{"name":2920,"color":2921},"good first issue","fbca04",{"name":2884,"color":2885},{"name":2924,"color":2925},"pages","00DFB5",15163,"Using only `router.options.ts` should enable page mode","2023-01-19T17:45:31Z","https://github.com/nuxt/nuxt/issues/15163",0.6366585,{"labels":2932,"number":2938,"owner":2874,"repository":2874,"state":2890,"title":2939,"updated_at":2940,"url":2941,"score":2942},[2933,2934,2935],{"name":2868,"color":2869},{"name":2920,"color":2921},{"name":2936,"color":2937},"2.x","d4c5f9",5621,"Default page","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/5621",0.6437388,{"description":2944,"labels":2945,"number":2948,"owner":2874,"repository":2874,"state":2890,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Environment\r\n\r\njust stackblitz, there is no issue with environment \r\n``` \r\n System:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 16.14.2 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 7.17.0 - /usr/local/bin/npm\r\n npmPackages:\r\n nuxt: ^2.16.2 => 2.16.2 \r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-a2pdyd?file=modules/addpage/_.vue\r\n\r\n### Describe the bug\r\n\r\nI'm not sure if it is a bug but, when there is no 'pages' directory in the Nuxt.js application, modules cannot add or extend routes. \r\n\r\nPlease check reproduction. There is no pages directory and we can see \r\n```\r\n WARN No pages directory found in /home/projects/github-a2pdyd. Using the default built-in page.\r\n```\r\n\r\nBut if you add pages directory then page file from module will be applicable. \r\n\r\nI have an idea to check if the 'pages' directory doesn't exist and then change the pages directory. \r\n## Is there any other option to force enabling it?\r\n\r\n\r\nHere is my temporary solution\r\n```js\r\nif (!fs.existsSync(this.options.srcDir + '/' + this.options.dir.pages)) {\r\n this.options.dir.pages = relative(\r\n this.options.srcDir,\r\n resolve(__dirname, './pages/')\r\n );\r\n }\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2946,2947],{"name":2887,"color":2888},{"name":2936,"color":2937},19699,"Modules can't add pages when pages directory not exist ","2024-06-30T09:21:58Z","https://github.com/nuxt/nuxt/issues/19699",0.64489883,{"description":2954,"labels":2955,"number":2958,"owner":2874,"repository":2874,"state":2890,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Describe the feature\r\n\r\nNuxt routing using folders is a nightmare for complex routes.\r\nCan I suggest a way to generate our custom router file without using the pages:extend hook?\r\n\r\nThe option to define a custom route in router.options.ts is also not good because Nuxt will not extend any new routes you return from the routes function with metadata defined in definePageMeta.\r\n\r\nWe should be able to choose to use a pre-generated routes with page directories or use our own custom rules routing file. With your own custom routing files we could be able to use everything from vue router like regex for matching route.\r\n\r\nThank you.\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2956,2957],{"name":2868,"color":2869},{"name":2884,"color":2885},25386,"Add a way to use our own custom routes without folder structure","2024-01-26T10:26:59Z","https://github.com/nuxt/nuxt/issues/25386",0.649063,{"description":2964,"labels":2965,"number":2969,"owner":2874,"repository":2874,"state":2890,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### Is your feature request related to a problem? Please describe.\r\nI have a detail page with a lot of information visualized in unique ways that only make sense to that page.\r\nBecause my `components` folder gets used for re-usable components, I have a subfolder in the same folder that route is located.\r\n\r\nMy `pages` folder looks a little something like this:\r\n```\r\nroutes\r\n- route-1\r\n - index.vue\r\n - -components\r\n - SomeComponentUniqueToThisRoute.vue\r\n - AnotherComponentUniqueToThisRoute.vue\r\n- route-2\r\n - index.vue\r\n - -components\r\n - SomeComponentUniqueToThisRoute.vue\r\n - AnotherComponentUniqueToThisRoute.vue\r\n .....\r\n```\r\n\r\nif I now go to `/route-2/-components/SomeComponentUniqueToThisRoute` it loads that component, obviously, because Nuxt thinks it's a page.\r\n\r\nIn the [documentation](https://nuxtjs.org/docs/2.x/directory-structure/pages#ignoring-pages) it says that I can already hide components by prefixing them with a `-`. But sadly this does not work on folders atm.\r\n\r\n### Describe the solution you'd like\r\nI want nuxt to **not** generate routes from `.vue` files in folders prefixed with a `-` by default, without the help of [.nuxtignore](https://nuxtjs.org/docs/2.x/configuration-glossary/configuration-ignore). Exactly like it already does for components.\r\n\r\nAll sub-folders and their .vue files should not be turned in to pages as well.\r\n\r\n### Describe alternatives you've considered\r\nHaving all components in my `-components` folder starting with a `-` would do the trick, but that is ugly and breaks vue's naming conventions.\r\n\r\nI could also write a couple of `.nuxtignore` rules that exclude the folders, but my application has many (around 25) -components folders that I would have to exclude. It is also another thing I have to explain to people who help me with this project, which isn't ideal.",[2966,2967,2968],{"name":2868,"color":2869},{"name":2884,"color":2885},{"name":2936,"color":2937},11497,"Feature request: Ability to ignore whole directories inside `pages`","2025-01-06T11:25:47Z","https://github.com/nuxt/nuxt/issues/11497",0.64925647,{"labels":2975,"number":2980,"owner":2874,"repository":2874,"state":2890,"title":2981,"updated_at":2982,"url":2983,"score":2984},[2976,2977],{"name":2884,"color":2885},{"name":2978,"color":2979},"bug","d73a4a",12013,"Nested Pages(NuxtPage) was not working","2023-01-19T15:53:23Z","https://github.com/nuxt/nuxt/issues/12013",0.65146387,["Reactive",2986],{},["Set"],["ShallowReactive",2989],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHnz5-NaQ4isz_NxSSZzMgTdZfUDSSGkwz7wwDiL8djI":-1},"/nuxt/nuxt/15060"]