\n\nI'm also using UModal, UCard elsewhere in the app itself, they do work there.\nSo what do I need to do to get these files parsed my vite/vue/nuxt ui?",[3165],{"name":3166,"color":3167},"question","d876e3",4892,"Using Nuxt UI in components from a npm package, in Vue","2025-09-05T08:48:22Z","https://github.com/nuxt/ui/issues/4892",0.7134665,{"description":3174,"labels":3175,"number":3181,"owner":3155,"repository":3155,"state":3157,"title":3182,"updated_at":3183,"url":3184,"score":3185},"### Describe the feature\n\n## **Main issue:** \n\nIt's a fact, `Nuxt` / `Vue app` are leaking all application URL(s) on hydration because the full router is shipped to the client (this is by design for the `Vue Router`).\n\nProblem: This allows attackers to get the full scope of your application as soon as they get to the first page, enlarging the potential attack surface by leaking your secret admin dashboard or other hidden URL .\n\n_Note: With only `Vue app`, your application is fully rendered in the client, making even all API routes string available without even passing the `Sign in` page, but as `Nuxt` brings `SSR` with it, (and if you do not write monkey code) this should no longer be the case._\n\nNowadays, more and more people use `Nuxt` with an `ORM` like `Prisma`, making it a real pain in the ass to setup a multi repo for each part of your app (who want's to pay **7$/user** a month to share a `Prisma schema` private module on `npm` ?). \n\n### **The questions are:** \n1. \"How to have 1 repo to rule them all and avoid to spread or copy interdependencies and components between repositories\" \n> I'm tired of looking at this:\n> ```\n> Github repository list:\n> - myproject-api \u003C--- prisma.schema\n> - myproject-user-dashboard \u003C--- prisma.schema + components like buttons\n> - myproject-admin-dashboard \u003C--- prisma.schema + components like buttons\n> - myproject-landing \u003C--- prisma.schema + components like buttons\n> ```\n> I want this:\n> ```\n> Github repository list:\n> - myproject 🎉\n> ```\n\n2. \"How to hide the existence of some section of my application\"\n> Why should the user receive all data about other section of the application that he should not be sniffing around ? \n\n3. \"How to use 1 app for all section but keeping them isolated of each other\"\n> Would be great to keep 1 server to render my web app even if it spitted in multiple sections right?\n\n## **Actual partial solution:** \nBuild distinct apps for each section of your app. One for the client, one for the admin etc... using `.env` variables and the `nuxt.config.ts` file's `ignore` property:\n\n**Building the client app without ignore:** \n\n\n**Building the client app with ignore:**\n\n\n### **Partial solution conclusion:** \nThis solve question 1 and 2, but what about question 3 ? I'm finding myself having to handle `1 container` / `node process` per section of my app... It's better, but... I don't need that much granularity.\n\n## **Another solution (feature request):**\nTo avoid to build and host multiple different apps for each section of your project : \n- 1 app for the landing pages + sign in\n- 1 app for the client dashboard\n- 1 app for the admin dashboard\n- etc...\n\nIt would be great to specify sections of the app that **Nuxt** would generate and serve independent router for.\n\n**Example:** \n```\n/pages \n - /landing \u003C-- 1 router for this section\n - /user \u003C-- 1 router for this section\n - /admin \u003C-- 1 router for this section\n```\n\n**Could be setup this way:** \n```ts\nexport default defineNuxtConfig({\n routers: {\n landing: [\"/pages/*.vue\",\"/pages/landing/**\"], \n user: [\"/pages/user/**\"],\n admin: [\"/pages/admin1234/**\"]\n ...\n }\n});\n```\n\n**This would generate 3 independent routers.**\n1. If the user goes to the landing page on `/`, it would be serve with the `landing` router, hiding the `user` and `admin` routes.\n2. If the user goes to the landing page on `/user`, it would be serve with the `user` router, hiding the `landing` and `admin` routes\n3. If the user goes to the landing page on `/admin1234`, it would be serve with the `admin` router, hiding the `landing` and `user` routes\n\n### **Feature solution conclusion:** \nThis should keep the evil at bay.\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).",[3176,3178],{"name":3146,"color":3177},"8DEF37",{"name":3179,"color":3180},"discussion","538de2",29872,"split section of your app via independent routers","2024-11-20T16:23:53Z","https://github.com/nuxt/nuxt/issues/29872",0.71510994,{"labels":3187,"number":3198,"owner":3155,"repository":3155,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},[3188,3189,3192,3195],{"name":3146,"color":3177},{"name":3190,"color":3191},"3.x","29bc7f",{"name":3193,"color":3194},"2.x","d4c5f9",{"name":3196,"color":3197},"⛔️ can be closed","484893",6707,"closed","Nuxt UI","2023-02-07T01:34:11Z","https://github.com/nuxt/nuxt/issues/6707",0.68432385,{"description":3205,"labels":3206,"number":3208,"owner":3155,"repository":3155,"state":3199,"title":3209,"updated_at":3210,"url":3211,"score":3212},"Not sure if this is supported. I'd like to use Nuxt to replace a somewhat complicated Vue/Webpack setup to generate JavaScript assets for a Phoenix app. As such, I don't want SSR at all. I just want the nice convention over configuration.\r\n\r\nIs there any way to do this currently? Static generation isn't quite what I want, because my app is still dynamic. I just don't want to use Nuxt as my server.\r\n\r\nThanks.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c163\">#c163\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3207],{"name":3193,"color":3194},192,"Build client-only bundle","2023-01-18T15:38:32Z","https://github.com/nuxt/nuxt/issues/192",0.6941448,{"description":3214,"labels":3215,"number":3218,"owner":3155,"repository":3156,"state":3199,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### Description\n\nWith Nuxt UI 3.02, configured for Vue, I was able to use it without vue-router. It now fails with 3.1 if it is not installed. I am in a slightly odd environment, in which I am using Astro with Vue client islands and Nuxt UI- so I understand this config is probably not supported. But, it was working with 3.02...just wondering if this is now required for 3.1 moving forward.\n\nOddly, it continues to work for any existing project, upgraded to 3.1. Its only on a new project or if an existing project is rebuilt (node_modules and lock file deleted) does it fail:\n\n[ERROR] Could not resolve \"vue-router\" imported by \"@nuxt/ui\". Is it installed?\n\nI scanned through the release notes and nothing jumped out regarding vue-router - so my apologies if it is mentioned there and I overlooked it.\n\nThanks.",[3216,3217],{"name":3166,"color":3167},{"name":3149,"color":3150},4038,"Does Nuxt UI 3.1 (configured for Vue) now require vue-router?","2025-05-02T17:17:41Z","https://github.com/nuxt/ui/issues/4038",0.69609106,{"description":3224,"labels":3225,"number":3227,"owner":3155,"repository":3156,"state":3199,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Description\n\nHello, I have read that with the Vercel and Nuxt collaboration that Nuxt UI/Pro will be licence free relatively soon and an new version will be create `v4`. My questions is, can we alreay make v3 license free because of this changes or do we need to wait for v4?\n\nThank you",[3226],{"name":3166,"color":3167},4595,"Nuxt UI Pro - Vercel and licence free on build?","2025-07-26T11:28:35Z","https://github.com/nuxt/ui/issues/4595",0.69671917,{"description":3233,"labels":3234,"number":3240,"owner":3155,"repository":3156,"state":3199,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Description\n\nas soon as i add \u003CUApp> around my app/app.vue file i begin to get errors like \n\n```\n[proxy]: WARN [nuxt] Your project has pages but the \u003CNuxtPage /> component has not been used. You might be using the \u003CRouterView /> component instead, which will not work correctly in Nuxt. You can set pages: false in nuxt.config if you do not wish to use the Nuxt vue-router integration.\n```\n\n\nor, if i just try to use nuxt ui PRO component they dont render on the screen (they show in the html) and i get abunch of hydration mismatch errors.\n\nam i doing something wrong?",[3235,3236,3239],{"name":3166,"color":3167},{"name":3237,"color":3238},"needs reproduction","CB47CF",{"name":3149,"color":3150},4603,"cannot get nuxt ui PRO working in a my nuxt 4 project","2025-07-26T15:06:28Z","https://github.com/nuxt/ui/issues/4603",0.70337415,{"description":3246,"labels":3247,"number":3252,"owner":3155,"repository":3156,"state":3199,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\n\nMy most sincere recommendation, I love Vue, Nuxt, Nuxtui, but the truth is that everything on the market is being made almost exclusively for React, including TailwindCSS, so I advise against having Pro, just the full Free UI and open-source, take it or leave it, you decide.\n\n### Version\n\n2.20.0\n\n### Reproduction\n\nnuxtui.com\n\n### Description\n\nMy most sincere recommendation, I love Vue, Nuxt, Nuxtui, but the truth is that everything on the market is being made almost exclusively for React, including TailwindCSS, so I advise against having Pro, just the full Free UI and open source, take it or leave it, you decide.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3248,3251],{"name":3249,"color":3250},"bug","d73a4a",{"name":3152,"color":3153},4297,"yes ui, no ui-pro","2025-06-05T19:46:12Z","https://github.com/nuxt/ui/issues/4297",0.70373845,{"description":3258,"labels":3259,"number":3261,"owner":3155,"repository":3155,"state":3199,"title":3262,"updated_at":3263,"url":3264,"score":3265},"Hi what is the best way to make something similiar to nuxtServerInit but without vuex?\r\n\r\ni have this scenario \r\n\r\non the first hit i want to build as example Footer / Header menu etc.. is there a way without vuex and nuxtServerInit something like fetch data in the layout and fill the component around or something??\r\n\r\ni searched but cant find any or just dont know how to search xD\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/c2539\">#c2539\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3260],{"name":3193,"color":3194},2925,"nuxtServerInit or something without vuex?","2023-01-18T16:09:43Z","https://github.com/nuxt/nuxt/issues/2925",0.7039409,["Reactive",3267],{},["Set"],["ShallowReactive",3270],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRTqQfw0rg8_coRUw3L9Ia80wq5nnidUyzGTMiUAnzuY":-1},"/nuxt/ui/4062"]