\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_",[2914,2915],{"name":2882,"color":2883},{"name":2892,"color":2893},20064,"\u003CNuxtPage> info message does not take custom pages dir into account","2023-04-04T13:18:31Z","https://github.com/nuxt/nuxt/issues/20064",0.6504204,{"labels":2922,"number":2933,"owner":2865,"repository":2865,"state":2866,"title":2934,"updated_at":2935,"url":2936,"score":2937},[2923,2924,2927,2930],{"name":2882,"color":2883},{"name":2925,"color":2926},"bug","d73a4a",{"name":2928,"color":2929},"cli","09F665",{"name":2931,"color":2932},"pages","00DFB5",11760,"Changing pages causes full nuxt restart","2023-01-19T15:47:38Z","https://github.com/nuxt/nuxt/issues/11760",0.6534528,{"description":2939,"labels":2940,"number":2949,"owner":2865,"repository":2865,"state":2866,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Describe the feature\n\nCurrently, the pages module has a very limited configuration option. It can be enabled/disabled and we can change the dir name. I would like to improve this to bring it on par with the configuration available for components and composables.\r\n\r\nExample: in the following directory structure I want to automatically load only Vue files (could be customizable with a glob pattern).\r\n```\r\npages\r\n somePage\r\n index.vue\r\n pageSpecificHelper.ts\r\n pageAsyncData.ts\r\n generated\r\n GQLGeneratedTypes.ts\r\n```\r\nCurrently, I have a couple of workarounds like adding `-` prefixes, or `ignore` config (though it affects all auto-imports).\r\n\r\nI would be happy to work on this myself. The idea I have would be to allow `pages` config to be an object with an option for `pattern` (or use the existing `ScanDir` interface for more configuration) and then change [this line in resolvePagesRoutes](https://github.com/nuxt/framework/blob/main/packages/nuxt/src/pages/utils.ts#L38) with fallback to the current pattern.\r\n\r\n---\r\n\r\nMore broadly speaking, I imagine that a more consistent and granular configuration of auto-imports would benefit many bigger projects. But this would be a bigger change affecting components, composables, plugins, and pages configuration. \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).",[2941,2942,2943,2946],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2944,"color":2945},"workaround available","11376d",{"name":2947,"color":2948},"❌ won't do","705B27",12333,"Improved pages module configuration","2024-11-28T05:07:59Z","https://github.com/nuxt/nuxt/issues/12333",0.6608799,{"description":2955,"labels":2956,"number":2959,"owner":2865,"repository":2865,"state":2866,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### 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_",[2957,2958],{"name":2882,"color":2883},{"name":2892,"color":2893},20801,"\u003CNuxtPage> info message does not look up for module pages","2023-05-15T12:47:31Z","https://github.com/nuxt/nuxt/issues/20801",0.66295207,{"description":2965,"labels":2966,"number":2969,"owner":2865,"repository":2865,"state":2866,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### Environment\n\nNuxt project info: \r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\n\n### Reproduction\n\n- Create a Nuxt module project:\r\n\r\n```\r\nnpx nuxi init -t module my-module\r\ncd my-module\r\nnpm i \r\nnpm run dev:prepare\r\n```\r\n\r\n- Make a call to `extendPages` within `module.ts` to add a page:\r\n\r\n```ts [module.ts]\r\nextendPages((pages) => {\r\n pages.push({\r\n name: 'module-page',\r\n path: '/:slug(.*)*',\r\n // @ts-ignore\r\n file: resolve(runtimeDir, './MyPage.vue')\r\n })\r\n})\r\n```\r\n- Add a page `~/src/runtime/MyPage.vue`:\r\n\r\n```vue [MyPage.vue]\r\n\u003Ctemplate>\r\n \u003Cdiv>Hello!\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n- Update `app.vue` to add `\u003CNuxtLayout>` and `\u003CNuxtPage>`:\r\n\r\n```vue [app.vue]\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtLayout>\r\n \u003CNuxtPage />\r\n \u003C/NuxtLayout>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n- Run the project with `npm run dev` and note that the page has not loaded:\r\n```\r\nPlugin by my-module!\r\n√ Vite server hmr 4 files in 50.259ms\r\n[Vue warn]: Failed to resolve component: NuxtPage\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\nPlugin by my-module!\r\n[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n√ Vite server hmr 4 files in 143.147ms\r\n[Vue warn]: Failed to resolve component: NuxtPage\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\nPlugin by my-module!\r\n```\n\n### Describe the bug\n\nNuxt cleverly strips out all router functionality if a project does not have a pages directory. However, this functionality is still removed if an installed module calls 'extendPages', so modules can't actually provide pages unless the project itself already has some, which may not always be the case.\r\n\r\nI think router functionality should be preserved by Nuxt if `extendPages` is called.\r\n\n\n### Additional context\n\nI am creating a module which creates a catch all page so I can do my own routing. I don't want to need to create a page in every project in order for my module's page to take effect. I can imagine other modules will want to act similarly, even if they're only providing more specific routes/pages.\n\n### Logs\n\n_No response_",[2967,2968],{"name":2882,"color":2883},{"name":2892,"color":2893},15060,"Nuxt does not include router functionality when a module calls extendPages unless the project has its own pages directory","2023-01-19T17:44:18Z","https://github.com/nuxt/nuxt/issues/15060",0.66975796,["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSzAS44iliTYLwdm7HxMMB8WXjt-g1kEEZm8Qaa22_wI":-1},"/nuxt/nuxt/13164"]