\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?",[3145],{"name":3146,"color":3147},"question","d876e3",4892,"ui","Using Nuxt UI in components from a npm package, in Vue","2025-09-05T08:48:22Z","https://github.com/nuxt/ui/issues/4892",0.7334486,{"description":3155,"labels":3156,"number":1674,"owner":3135,"repository":3157,"state":3158,"title":3159,"updated_at":3160,"url":3161,"score":3162},"https://vercel.com/account/login-connections\n\n",[],"nuxt.com","closed","Login connections page `/account/login-connections`","2023-02-15T12:31:40Z","https://github.com/nuxt/nuxt.com/issues/39",0.46984798,{"description":3164,"labels":3165,"number":3172,"owner":3135,"repository":3135,"state":3158,"title":3173,"updated_at":3174,"url":3175,"score":3176},"Not sure if this belongs here. Feels like it doesn't belong in the Nuxt repo either, because it's module specific. Let me know if I need to move it.\r\n\r\nSo my situation is the following. I'm further improving my [Nuxt-vuetify module](https://github.com/invictus-codes/nuxt-vuetify). Users of the module, will provide a Vuetify config through the Nuxt.config.ts. Now Vuetify has the following feature when it comes to icons, [fa-svg](https://vuetifyjs.com/en/features/icon-fonts/#font-awesome-svg-icons). To use this feature, you need to provide a function as iconSet (component). This is how it works, I cannot change this. However, this is not the cause of my \"issue\".\r\n\r\nWhat I can't seem to get working is the following, tested it on the nuxt-module-starter:\r\n\r\nIn my Nuxt.config.ts:\r\n```typescript\r\nexport default defineNuxtConfig({\r\n modules: [\"../src/module\"],\r\n myModule: {\r\n testViaConfig() {\r\n console.log(\"test\");\r\n return \"test\";\r\n },\r\n },\r\n});\r\n```\r\n\r\nin my module.ts:\r\n```typescript\r\nimport { defineNuxtModule, addPlugin, createResolver } from \"@nuxt/kit\";\r\n\r\n// Module options TypeScript interface definition\r\nexport interface ModuleOptions {}\r\n\r\nexport default defineNuxtModule\u003CModuleOptions>({\r\n meta: {\r\n name: \"my-module\",\r\n configKey: \"myModule\",\r\n },\r\n // Default configuration options of the Nuxt module\r\n defaults: {},\r\n setup(options, nuxt) {\r\n const resolver = createResolver(import.meta.url);\r\n\r\n nuxt.options.runtimeConfig.public.myModule = {\r\n ...options,\r\n test: \"runtimeConfig, check\",\r\n testViaModule: () => {\r\n console.log(\"test\");\r\n return \"test\";\r\n },\r\n };\r\n // Do not add the extension since the `.ts` will be transpiled to `.mjs` after `npm run prepack`\r\n addPlugin(resolver.resolve(\"./runtime/plugin\"));\r\n },\r\n});\r\n```\r\n\r\nIn my runtime/plugin.ts:\r\n```typescript\r\nimport { defineNuxtPlugin, useRuntimeConfig } from \"#app\";\r\n\r\nexport default defineNuxtPlugin((nuxtApp) => {\r\n const config = useRuntimeConfig();\r\n const options = config.public.myModule;\r\n console.log({ options });\r\n console.log(\"Plugin injected by my-module!\");\r\n});\r\n```\r\n\r\nI would expect that in the browser both the `testViaConfig` and `testViaModule` functions would be logged. Except only the string (defined in module.ts, also passed via runtimeConfig), is logged in the browser.\r\n\r\nI have made a codesandbox to reproduce. You can find it [here](https://codesandbox.io/p/github/jvhellemondt/nuxt-module-starter/draft/trusting-galileo?file=%2Fsrc%2Fmodule.ts&workspaceId=26bac05a-e35e-485b-bb0f-53f697bee73f).\r\n\r\nIs it intended that I cannot pass functions to runtime like this? I have the feeling that it's not possible due to rollup, however I'm definitely not an expert on that. If so, is there another way around? It seems vital that users of the module can provide it via the Nuxt.config.ts from a user experience perspective.\r\n\r\nHope someone is able to help out. If I need to explain further, please let me know.\r\n\r\nThank you in advance.\r\n\r\nBest regards,\r\n\r\nJ",[3166,3169],{"name":3167,"color":3168},"3.x","29bc7f",{"name":3170,"color":3171},"pending triage","E99695",20933,"Question/ bug: How to provide functions from within Nuxt.config.ts or module.ts to runtime?","2024-04-17T06:42:23Z","https://github.com/nuxt/nuxt/issues/20933",0.71934545,{"description":3178,"labels":3179,"number":3180,"owner":3135,"repository":3136,"state":3158,"title":3181,"updated_at":3182,"url":3183,"score":3184},"Although it looks redundant, Iconify uses `\u003CIcon icon=\"...\" />` as the Vue component. Since this module uses Iconify, why not keeping the same structure so we can just copy the component from their lib? An alias prop would be welcomed if I'm sounding too radical 😋 That way we can use both `name` and `icon`.",[],51,"[question] Why not using `icon` as a prop instead of `name`?","2023-02-16T15:53:34Z","https://github.com/nuxt/icon/issues/51",0.72326237,{"description":3186,"labels":3187,"number":1044,"owner":3135,"repository":3136,"state":3158,"title":3188,"updated_at":3189,"url":3190,"score":3191},"Please add to readme file nuxt3 dynamic import example:\r\n\r\n\r\n```\r\nimport { Icon } from \"@iconify/vue\"\r\n\r\nfunction renderIcon(icon) {\r\n return () => h(Icon, { icon })\r\n}\r\n\r\nrenderIcon('uil:github')\r\n```\r\n\r\n",[],"Please add to readme file nuxt3 dynamic import ","2022-11-07T10:46:55Z","https://github.com/nuxt/icon/issues/22",0.7244425,{"description":3193,"labels":3194,"number":1044,"owner":3135,"repository":3157,"state":3158,"title":3195,"updated_at":3196,"url":3197,"score":3191},"The http call can be left commented for now. However, the confirm method: https://github.com/docusgen/docus.com/blob/dev/pages/_team/settings/index.vue#L206, should be replaced by the `AlertDialog` component: https://github.com/nuxtlabs/nuxt.com/blob/dev/pages/account/teams.vue#L78\n\n\n",[],"Leave team in `/:team/settings`","2023-02-15T12:30:31Z","https://github.com/nuxt/nuxt.com/issues/22",{"description":3199,"labels":3200,"number":1044,"owner":3135,"repository":3201,"state":3158,"title":3202,"updated_at":3203,"url":3204,"score":3191},"Scripts that should be added before release:\r\n\r\n**Analytics**\r\n- [x] Plausible\r\n\r\n**Payments**\r\n- [x] [LemonSqueezy](https://docs.lemonsqueezy.com/guides/developer-guide/lemonjs)\r\n\r\n",[],"scripts","Third Party Register Scripts To Add","2024-04-22T12:56:34Z","https://github.com/nuxt/scripts/issues/22",{"description":3206,"labels":3207,"number":3211,"owner":3135,"repository":3135,"state":3158,"title":3212,"updated_at":3213,"url":3214,"score":3215},"Hi folks, I trying to extend a Vuetify component in a nuxt project (nuxt starter template) but i'm getting errors...\r\n\r\nMy extended component: \r\n```js \r\n// /assets/components/vuetifyExtended/VRadioGroup/VRadioIcon.js\r\n\r\nimport VRadio from 'vuetify/src/components/VRadioGroup/VRadio';\r\n\r\nexport default {\r\n name: 'v-radio-icon',\r\n extends: VRadio,\r\n props: {\r\n iconActive: { type: String, default: 'radio_button_checked' },\r\n iconInactive: { type: String, default: 'radio_button_unchecked' },\r\n },\r\n computed: {\r\n icon() {\r\n return this.isActive ? this.iconActive : this.iconInactive;\r\n },\r\n },\r\n};\r\n```\r\n\r\nThe kind of errors i'm getting:\r\n```sh\r\n[...]\r\n ERROR Failed to compile with 2 errors 08:29:45\r\n\r\nerror in ./node_modules/vuetify/src/util/helpers.js\r\n\r\nModule parse failed: Unexpected token (34:28)\r\nYou may need an appropriate loader to handle this file type.\r\n| context.data.on = context.data.on || {}\r\n| if (!Object.isExtensible(context.data.on)) {\r\n| context.data.on = { ...context.data.on }\r\n| }\r\n|\r\n@ ./node_modules/vuetify/src/components/transitions/index.js 1:0-4:27\r\n@ ./node_modules/vuetify/src/components/VRadioGroup/VRadio.js\r\n[...]\r\n```\r\n\r\nI've seen that [issue](https://github.com/vuetifyjs/vuetify/issues/1840) but the solution did not solved mine. \r\nDoes anyone can help me ? :) thx!\r\n\r\n\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/c2719\">#c2719\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3208],{"name":3209,"color":3210},"2.x","d4c5f9",3139,"Extending a vuetify component","2023-01-18T16:10:06Z","https://github.com/nuxt/nuxt/issues/3139",0.72593457,{"description":3217,"labels":3218,"number":3219,"owner":3135,"repository":3136,"state":3158,"title":3220,"updated_at":3221,"url":3222,"score":3223},"In my own projects I want to name how I build the component \"Icon\".\r\n\r\nI think as a package it would make way more sense for the component name to be \"NuxtIcon\" with an \"icon\" class instead of just \"Icon\" with name.\r\n\r\nAlso see this:\r\nhttps://vuejs.org/style-guide/rules-essential.html#use-multi-word-component-names\r\n(not super relevant due to how I would use it probably lol)\r\n\r\nI'd like to look at my own codebase and make the icon component custom, like:\r\n\r\n```html\r\n\u003C!-- Icon.vue -->\r\n\u003Ctemplate>\r\n\u003Cdiv class=\"aspect-square rounded-full h-20 text-2xl flex items-center justify-center text-white\">\r\n \u003CNuxtIcon :icon=\"icon\" />\r\n\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\ndefineProps({ icon: String })\r\n\u003C/script>\r\n```",[],174,"Can the Base component be changed to \"NuxtIcon\" instead of \"Icon\" with the \"name\" attribute?","2024-06-26T16:45:07Z","https://github.com/nuxt/icon/issues/174",0.7268626,["Reactive",3225],{},["Set"],["ShallowReactive",3228],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fK7nomuLHYMTAzsQT0T85kaxWSbxZYsXxVKL74ULKv0w":-1},"/nuxt/icon/39"]