\u003C/svg>\n \u003C/div>\n \u003C/ScriptIntercom>\n\u003C/template>\n```\n\n\n\n",[1984],{"name":1985,"color":1986},"bug","d73a4a",321,"nuxt","scripts","closed","Intercom chat window doesn't appear","2024-11-18T13:58:42Z","https://github.com/nuxt/scripts/issues/321",0.45197397,{"description":1996,"labels":1997,"number":2007,"owner":1988,"repository":1988,"state":1990,"title":2008,"updated_at":2009,"url":2010,"score":2011},"### Describe the feature\n\nI'm trying migrate my vue3 project to nuxt3, but find many problems.\r\nJust as below codes, nuxtPage cannot get its rendering component, but the router-view has such api to achieve it. \r\n\r\n```\r\n \u003Crouter-view :style=\"viewStyle\" v-slot=\"{ Component }\">\r\n \u003Ccomponent :is=\"Component\" />\r\n \u003C/router-view>\r\n \u003Crouter-view :style=\"viewStyle\" name=\"user\" v-slot=\"{ Component }\">\r\n \u003Ctransition appear name=\"slide\">\r\n \u003Ccomponent :is=\"Component\" />\r\n \u003C/transition>\r\n \u003C/router-view> \r\n```\r\nIn nuxt3 I cannot use nuxtPage to achieve the same effect of above codes.\r\nSeems NuxtPage neither get its rendering component nor add addtional style to its rendering component .\r\nHence need NuxtPage to get its rendering component to achieve the dynamic component feature in vue3. Thx!\r\n\r\n\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [X] 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).",[1998,2001,2004],{"name":1999,"color":2000},"enhancement","8DEF37",{"name":2002,"color":2003},"discussion","538de2",{"name":2005,"color":2006},"3.x","29bc7f",24670,"allow passing props directly to page via `\u003CNuxtPage>`","2023-12-14T04:13:01Z","https://github.com/nuxt/nuxt/issues/24670",0.6909514,{"description":2013,"labels":2014,"number":2024,"owner":1988,"repository":1988,"state":1990,"title":2025,"updated_at":2026,"url":2027,"score":2028},"### Version\r\n\r\n[v2.3.4](https://github.com/nuxt.js/releases/tag/v2.3.4)\r\n\r\n### Reproduction link\r\n\r\n[https://codesandbox.io/s/r7l358z6xo](https://codesandbox.io/s/r7l358z6xo)\r\n\r\n### Steps to reproduce\r\n\r\nuse @nuxtjs/router and use your own router.js file\r\ncreate a route with a meta prop in your router.js file\r\nuse middleware, notice your route's meta isn't in the context.route.meta, it's only in context.route.matched[0].meta\r\n\r\nSeems like a bug\r\n\r\n### What is expected ?\r\n\r\nIt seems like you are trying to make route.meta some type of array of metas from components. \r\n\r\nThe docs say it's a vue-router route obj, but it doesn't really seem to act like one. I would assume at the very least real route metas would be in route.meta\r\n\r\n### What is actually happening?\r\n\r\nroute metas are not in route.meta, you have to look at the matched routes instead :(\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8438\">#c8438\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2015,2018,2021],{"name":2016,"color":2017},"available soon","6de8b0",{"name":2019,"color":2020},"pending triage","E99695",{"name":2022,"color":2023},"2.x","d4c5f9",4725,"vue-router metas not merged with component metas in middleware","2023-01-22T15:30:09Z","https://github.com/nuxt/nuxt/issues/4725",0.70007396,{"description":2030,"labels":2031,"number":2034,"owner":1988,"repository":1988,"state":1990,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### What problem does this feature solve?\n\nI'm trying to find a way to read `props` from every .vue component in the project and write the result to a JSON file.\n\nIt should happen server side so I've tried creating a custom nuxt command and a module. The problem with these is I can't actually import a component, it's just a syntax error because components are not just JS. Even after a `nuxt build` when the components are reduced to being just JS in the `.nuxt` folder I still couldn't figure out how to read the props from that mess. I spent a few days on google, reading other modules, nuxt documentation and source code but couldn't find a way to extract details about components.\n\nWhat does work is a plugin in server only mode. I can read and write files, import components, read the props. Basically everything I wanted. But now the issue is that it's a plugin and that's not what plugins are for. This script should only run once during build but a plugin will run on every page load.\n\nSo I'd like to see a generally good way of messing with components from a command line script.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9773\">#c9773\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2032,2033],{"name":1999,"color":2000},{"name":2022,"color":2023},6411,"Using components in modules","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6411",0.70115197,{"description":2040,"labels":2041,"number":2044,"owner":1988,"repository":2045,"state":1990,"title":2046,"updated_at":2047,"url":2048,"score":2049},"",[2042],{"name":1999,"color":2043},"1ad6ff",359,"nuxt.com","Fetch components from project url `/api/component-meta`","2022-04-19T13:51:35Z","https://github.com/nuxt/nuxt.com/issues/359",0.7033901,{"description":2051,"labels":2052,"number":2044,"owner":1988,"repository":2053,"state":1990,"title":2054,"updated_at":2055,"url":2056,"score":2049},"Update e2e section to use `@nuxt/test-utils`\r\n\r\nhttps://nuxtjs.org/guide/development-tools#end-to-end-testing",[],"test-utils","update e2e section in nuxtjs.org","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/359",{"labels":2058,"number":2061,"owner":1988,"repository":1988,"state":1990,"title":2062,"updated_at":2063,"url":2064,"score":2065},[2059,2060],{"name":1999,"color":2000},{"name":2022,"color":2023},8227,"Can we export nuxt project as web components ?","2023-02-14T11:31:45Z","https://github.com/nuxt/nuxt/issues/8227",0.7061766,{"description":2067,"labels":2068,"number":2070,"owner":1988,"repository":1988,"state":1990,"title":2071,"updated_at":2072,"url":2073,"score":2074},"I've been trying to get access to the `meta` field in `this.$route` in the `404.vue` page component. I copied the extendedRoutes example from [here](https://github.com/nuxt/docs/blob/master/en/api/configuration-router.md) and appended `meta` like below:\r\n\r\n```javascript\r\nmodule.exports = {\r\n router: {\r\n extendRoutes (routes, resolve) {\r\n routes.push({\r\n name: 'custom',\r\n path: '*',\r\n component: resolve(__dirname, 'pages/404.vue'),\r\n meta: { name: 'Pumpkin', age: 19 }\r\n })\r\n }\r\n }\r\n}\r\n```\r\n\r\nI'm getting undefined when we access the above `name` variable using meta property. Although, the vue-router documentation says we can access it correctly [here](https://router.vuejs.org/en/advanced/meta.html)\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c777\">#c777\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2069],{"name":2022,"color":2023},906,"Accessing the meta fields in extendedRoutes defined in nuxt config","2023-01-18T22:19:40Z","https://github.com/nuxt/nuxt/issues/906",0.7073983,{"labels":2076,"number":2079,"owner":1988,"repository":1988,"state":1990,"title":2080,"updated_at":2081,"url":2082,"score":2083},[2077,2078],{"name":1999,"color":2000},{"name":2005,"color":2006},13413,"Support for explicit import global components","2024-12-22T03:26:07Z","https://github.com/nuxt/nuxt/issues/13413",0.7074061,{"description":2085,"labels":2086,"number":2090,"owner":1988,"repository":1988,"state":1990,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### 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.",[2087,2088,2089],{"name":1999,"color":2000},{"name":2005,"color":2006},{"name":2022,"color":2023},11497,"Feature request: Ability to ignore whole directories inside `pages`","2025-01-06T11:25:47Z","https://github.com/nuxt/nuxt/issues/11497",0.70740896,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"UItzx4IPdjqaEZH9JrmCVw2fyIA9gLGgTU1RJ86TIxk":-1},"/nuxt/nuxt.com/321"]