\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT9fUh9cK0d\n\nAfter change `1` transforms to `\"1\"` and got error in console.",[3171,3172,3175],{"name":3140,"color":3141},{"name":3173,"color":3174},"duplicate","cfd3d7",{"name":3160,"color":3161},2886,"USelect converts integer value to string","2025-01-09T14:22:11Z","https://github.com/nuxt/ui/issues/2886",0.671276,{"description":3182,"labels":3183,"number":3184,"owner":3146,"repository":3185,"state":3163,"title":3186,"updated_at":3187,"url":3188,"score":3189},"Open https://nuxt.com/docs/guide/directory-structure/composables, **Introduction** page is shown instead of **Composables**\n\n\n\nI think the regression is due to 43b0f43",[],1752,"nuxt.com","All docs/[...slug] routes show Introduction page","2025-01-14T11:25:53Z","https://github.com/nuxt/nuxt.com/issues/1752",0.67293316,{"description":3191,"labels":3192,"number":3193,"owner":3146,"repository":3194,"state":3163,"title":3195,"updated_at":3196,"url":3197,"score":3198},"Docs: https://posthog.com/docs/libraries/js\r\n\r\nFor reference this is how I currently instrument it:\r\n\r\n```\r\nimport { Capacitor } from '@capacitor/core'\r\nimport { posthog } from 'posthog-js'\r\nimport { appVersion } from '~/shared/version'\r\n\r\nexport default defineNuxtPlugin({\r\n name: 'analytics',\r\n setup() {\r\n if (import.meta.env.TEST) {\r\n return\r\n }\r\n\r\n const config = useRuntimeConfig()\r\n const router = useRouter()\r\n\r\n if (config.public.analyticsReportingEnabled) {\r\n posthog.init(config.public.posthog.dsn, {\r\n capture_pageview: false,\r\n capture_pageleave: true,\r\n api_host: config.public.posthog.apiHost,\r\n disable_session_recording: true,\r\n advanced_disable_decide: true,\r\n advanced_disable_feature_flags: true,\r\n advanced_disable_feature_flags_on_first_load: true,\r\n enable_recording_console_log: false,\r\n autocapture: false\r\n })\r\n\r\n posthog.register({\r\n environment: config.public.appEnvironment,\r\n countryCode: config.public.appCountryCode,\r\n release: appVersion,\r\n platform: Capacitor.getPlatform(),\r\n native: Capacitor.isNativePlatform()\r\n })\r\n\r\n router.afterEach(to => {\r\n posthog.capture('$pageview', {\r\n $current_url: to.fullPath\r\n })\r\n })\r\n }\r\n\r\n return {\r\n provide: {\r\n analytics: posthog\r\n }\r\n }\r\n }\r\n})\r\n```\r\n\r\nand after the user has logged in or we detect they are already logged in on page load:\r\n\r\n```\r\nthis.analytics.identify(userId, {\r\n email\r\n roles\r\n})\r\n ```\r\n \r\n Thanks!\r\n\r\n",[],206,"scripts","Suggestion: Posthog [analytics]","2024-09-03T16:06:49Z","https://github.com/nuxt/scripts/issues/206",0.6800845,{"description":3200,"labels":3201,"number":3206,"owner":3146,"repository":3207,"state":3163,"title":3208,"updated_at":3209,"url":3210,"score":3211},"I've explored other font providers, looks like `fontsource` is also quite promising.\r\n\r\nCurrently most of its fonts are from Google Fonts, along with some icons and some other fonts. It's also the service that Cloudflare Fonts is fetching from.\r\n\r\n@danielroe Would you like to include this font provider? If so, I'd like to work on it.\r\n\r\nDocs: https://fontsource.org/docs",[3202,3203],{"name":3157,"color":3158},{"name":3204,"color":3205},"provider","1161A4",65,"fonts","feat: fontsource provider","2024-03-20T13:12:12Z","https://github.com/nuxt/fonts/issues/65",0.68269897,{"description":3213,"labels":3214,"number":3218,"owner":3146,"repository":3219,"state":3163,"title":3220,"updated_at":3221,"url":3222,"score":3223},"While working on a new project with new developers we stumbled upon this silent failure.\r\nWe had Icons exported from Figma in the format:\r\n\r\n- iconCalendar.svg\r\n- iconPerson.svg\r\n- ...\r\n\r\nWhich were then loaded as customCollection via NuxtConfig\r\n\r\n```\r\nicon: {\r\n customCollections: [\r\n {\r\n prefix: 'theme-icon',\r\n dir: './assets/icons'\r\n },\r\n ],\r\n },\r\n```\r\n\r\nThe message upon restart was reassuring that all icons were loaded and should be accessible.\r\n\r\n```\r\nNuxt Icon loaded local collection theme-icon with 43 icons.\r\n```\r\n\r\n\r\nBut we could not access them, or better said, we could only access the ones which only were lowercase. So I digged down the whole integration with the following waypoints:\r\n\r\n- https://github.com/nuxt/icon/blob/main/src/collections.ts\r\n- https://github.com/nuxt/icon/blob/main/src/runtime/components/svg.ts#L41\r\n- https://github.com/iconify/iconify/blob/main/components/vue/src/iconify.ts#L18\r\n- https://github.com/iconify/iconify/blob/main/packages/core/src/storage/functions.ts#L86\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L23\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L90\r\n\r\nIn words:\r\n\r\n- The collection gets loaded and auto-detects all svg files within the collection folder. It also validates if the content is valid and loads them into the internal collection of nuxt-icon. \r\n- Then when called by the Component integration it gets converted/added to the Iconify component which then goes down its library path to add it to the/a custom collection for display.\r\n- This in fact validates the name given and will NOT add it if its invalid thus not displaying any icon with invalid names.\r\n- No error handling is done for this in the Component (addIcon in fact returns success which could be handled)\r\n- No validation is done when creating/loading the nuxt-icon collection.\r\n\r\n---\r\n\r\n**Suggested resolution:** For better DX there should also be a name validation when loading the collection and it should warn about all icons not following the convention. I can craft the corresponding PR.\r\n\r\n---\r\n\r\nDid I miss something elsewhere or is my deduction of the error correct?",[3215],{"name":3216,"color":3217},"upstream","B4199A",257,"icon","Invalid Icon filenames, as defined/validated by Iconify, are silently failing","2024-11-21T18:24:05Z","https://github.com/nuxt/icon/issues/257",0.68435055,{"description":3225,"labels":3226,"number":3229,"owner":3146,"repository":3147,"state":3163,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Description\n\nNuxt UI should have the potential to open native links in a Nuxt UI Modal by simply adding a certain `modal` parameter in [NuxtLink](https://nuxt.com/docs/api/components/nuxt-link).\n\n`\u003CNuxtLink to=\"/about\" modal>About page shown in modal but can also be opened natively (e.g. new tab)\u003C/NuxtLink>`\n\nThe link should still be a native link with progressive enhancement, so _if users would like to open the URL in a new tab, they can do_! If not, it will open the content in a modal.\n\nThat would be great DX and UX! 🎉\n\nThe `modal` property is just one possible solution, maybe there's even a better one using a native HTML property like `rel=\"modal\"`, we should discuss that.\n\nIn future versions there might be further control parameters to override the defaults for\n\n- modal size\n- modal style\n- modal opacity\n- ...\n\nBut let's start simple.\n\nSomething similar was done here, but I think this should really be part of Nuxt UI or even Nuxt Core.\nhttps://nuxt-pages-plus.pages.dev/components/plus-modal-link\n\n### Additional context\n\n_No response_",[3227,3228],{"name":3157,"color":3158},{"name":3160,"color":3161},3298,"Enhance NuxtLink to open in Modal using a \"modal\" property","2025-03-08T12:21:53Z","https://github.com/nuxt/ui/issues/3298",0.6869145,{"description":3235,"labels":3236,"number":3240,"owner":3146,"repository":3147,"state":3163,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.5.0\n- Nuxt Version: -\n- CLI Version: 3.23.0\n- Nitro Version: -\n- Package Manager: pnpm@10.6.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button#label\n\n### Description\n\nthe buttons should have cursor pointer by default.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3237,3238,3239],{"name":3140,"color":3141},{"name":3173,"color":3174},{"name":3160,"color":3161},3552,"Button | should have `cursor-pointer` by default","2025-03-19T20:46:13Z","https://github.com/nuxt/ui/issues/3552",0.6892209,{"description":3246,"labels":3247,"number":3256,"owner":3146,"repository":3146,"state":3163,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n```\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.0\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: vite, extensions\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-o84u83\n\n### Describe the bug\n\nI have been looking to add a very small number (2-3) of pages to a Nuxt 3 project using Markdown. Since I'll only using Markdown for a few pages in the project and don't need additional features like querying, I thought I'd try using [vite-plugin-vue-markdown](https://github.com/mdit-vue/vite-plugin-vue-markdown) instead of the heavier Nuxt Content.\r\n\r\nI changed the Vite settings in `nuxt.config.ts` according to `vite-plugin-vue-markdown`'s documentation and added `.md` to the `extensions` array. However, this does not seem to be sufficient to get `vite-plugin-vue-markdown` and the Nuxt page resolver to work together since when I visit a page written using a Markdown file, I run into the following errors (as if `vite-plugin-vue-markdown` hasn't ran at all):\r\n\r\nServer\r\n```\r\nERROR At least one \u003Ctemplate> or \u003Cscript> is required in a single file component.\r\n```\r\nBrowser\r\n```\r\n500\r\n[vite-node] [plugin:vite:vue] [SyntaxError] /pages/about.md?macro=true\r\n\r\n# About Page\r\n\r\nat /pages/about.md?macro=true\r\nat Object.parse$4 [as parse] (./node_modules/@vue/compiler-sfc/dist/compiler-sfc.cjs.js:5269:21)\r\nat createDescriptor (file://./node_modules/@vitejs/plugin-vue/dist/index.mjs:86:43)\r\nat transformMain (file://./node_modules/@vitejs/plugin-vue/dist/index.mjs:2240:34)\r\nat TransformContext.transform (file://./node_modules/@vitejs/plugin-vue/dist/index.mjs:2738:16)\r\nat Object.transform (file://./node_modules/vite/dist/node/chunks/dep-79892de8.js:43436:44)\r\nat async loadAndTransform (file://./node_modules/vite/dist/node/chunks/dep-79892de8.js:41154:29)\r\n```\n\n### Additional context\n\nI have been able to partially get the Vite plugin working in Nuxt by manually importing the routes using `app/router.options.ts` (https://stackblitz.com/edit/github-dbvb63), although this workaround interferes with other Nuxt features like import aliases:\r\n```\r\n[nuxt] #imports should be transformed with real imports. There seems to be something wrong with the imports plugin.\r\n```\r\n\r\nPer the instructions for reporting bugs, I have also tried using the Vite plugin with the Vue 3 SSR template and it seems to work fine there (https://stackblitz.com/edit/github-uo229m).\n\n### Logs\n\n_No response_",[3248,3251,3253],{"name":3249,"color":3250},"3.x","29bc7f",{"name":3216,"color":3252},"E8A36D",{"name":3254,"color":3255},"🔨 p3-minor","FBCA04",20245,"Incompatibility when using `.md` pages through `vite-plugin-vue-markdown`","2023-04-13T21:45:30Z","https://github.com/nuxt/nuxt/issues/20245",0.69024634,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLuMRN_dsiu5gQ5-6dZ6SCt8bjqkvqSe8c-MR0MmLlPQ":-1},"/nuxt/ui/2805"]