`\n\nUnable to use stroke-width does not take effect",[],364,"nuxt","icon","open","Unable to use stroke-width does not take effect","2025-03-04T02:48:19Z","https://github.com/nuxt/icon/issues/364",0.7055651,{"description":1993,"labels":1994,"number":2001,"owner":1985,"repository":2002,"state":1987,"title":2003,"updated_at":2004,"url":2005,"score":2006},"### Description\n\nSupport either Nuxt config override or feat a config option to override prefetch behavior.\n\nThe default behavior of internal links are `prefetchOn: { visibility: true }` in Nuxt.\n\nChanging it only affects `\u003CNuxtLink>`. Nuxt UI components featuring links ignore this parameter and preserve prefetching on visibility.\n\n```ts\n// nuxt.config.ts \n experimental: {\n defaults: {\n nuxtLink: {\n // Don't affect Nuxt UI components\n prefetchOn: { interaction: true, visibility: false },\n },\n },\n },\n```\n\nI can add props on each component (`no-prefetch` or `prefetch-on=\"interaction\"`) thought but could be comfort to be able to change the default behavior \n\nThanks.\n\n### Additional context\n\n_No response_",[1995,1998],{"name":1996,"color":1997},"enhancement","a2eeef",{"name":1999,"color":2000},"triage","ffffff",3263,"ui","[Feature request] option default links prefetch behavior","2025-02-07T10:00:36Z","https://github.com/nuxt/ui/issues/3263",0.7163632,{"description":2008,"labels":2009,"number":2013,"owner":1985,"repository":2014,"state":1987,"title":2015,"updated_at":2016,"url":2017,"score":2018},"### Environment\n\nThis is one of the environments i came across the problem:\r\n[11:15:23 AM] Working directory: /Users/lorenzorottigni/Documents/gitlab_private/portfolio.rottigni.tech\r\n[11:15:23 AM] Nuxt project info: (copied to clipboard)\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.13.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: vite\r\n- User Config: ssr, debug, srcDir, serverDir, test, app, modules, css, postcss, unocss, tailwindcss, googleFonts, i18n, nitro, pwa, image, delayHydration, extensions, typescript, builder, vite, vue, runtimeConfig, devServer, sourcemap, experimental\r\n- Runtime Modules: @vueuse/nuxt@10.7.2, @nuxtjs/tailwindcss@6.10.4, @pinia/nuxt@0.5.1, @unocss/nuxt@0.58.3, @nuxtjs/i18n@8.0.0, @nuxt/image@1.3.0, nuxt-jsonld@2.0.8, @kevinmarrec/nuxt-pwa@0.17.0, @nuxtjs/google-fonts@3.1.3, nuxt-calendly@0.1.18, nuxt-delay-hydration@1.3.3, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n[11:15:23 AM] 👉 Report an issue: https://github.com/nuxt/nuxt/issues/new\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\n\n### Reproduction\n\nThe crucial file is MyComponent.spec.ts:\r\nhttps://stackblitz.com/~/github.com/LorenzoRottigni/nuxt-test-utils-vitest-spy\n\n### Describe the bug\n\nI'm currently facing challenges in testing a component method within a Nuxt environment. Specifically, I'm attempting to spy on a component method to test its interactions within template events. Despite researching similar cases online, I've yet to find a clear solution to this issue.\r\n\r\nOne suggestion I encountered was to define the spy before the component mounts. However, I'm unable to access `wrapper.vm` before mount time, complicating this approach. Additionally, I experimented with spying on the global injected `$fetch` method from the 'ofetch' library. Unfortunately, this led to another error regarding the inability to redefine the variable `$fetch` when attempting variations like:\r\n\r\n```javascript\r\nimport OFetch from 'ofetch'\r\nconst spy = vi.spyOn(OFetch, '$fetch')\r\n// or\r\nconst spy = vi.spyOn(global, '$fetch')\r\n// or\r\nconst spy = vi.spyOn({ $fetch }, '$fetch')\r\n```\r\n\r\nIt appears that this issue may not be directly tied to the nuxt-test-utils package. Nevertheless, I wanted to bring it to your attention in the hopes that someone might offer guidance or assistance. I'm eager to find a resolution and would appreciate any insights or suggestions you might have.\r\n\r\nI'm also considering reporting a similar issue to the vue-test-utils package, as I suspect that this problem might be reproducible outside of the Nuxt environment.\r\n\r\nThank you for your time and assistance.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2010],{"name":2011,"color":2012},"pending triage","5D08F5",763,"test-utils","Unable to use vitest spy within nuxt 3 component methods.","2024-05-28T15:28:23Z","https://github.com/nuxt/test-utils/issues/763",0.7232378,{"description":2020,"labels":2021,"number":2027,"owner":1985,"repository":2002,"state":1987,"title":2028,"updated_at":2029,"url":2030,"score":2031},"### Description\n\nIs there any chance we can get option to enable/disable collapsible when collapsed prop is true. v3.0.0-alpha.13 'fixed' NavigationMenu: disable collapsible with collapsed prop, i used nuxt ui since v3.0.0-alpha.12 and thought the collapsible when collapsed was feature.\n\n### Additional context\n\n_No response_",[2022,2023,2026],{"name":1996,"color":1997},{"name":2024,"color":2025},"v3","49DCB8",{"name":1999,"color":2000},3353,"NavigationMenu: Option to enable collapsible with collapsed prop","2025-02-27T07:38:30Z","https://github.com/nuxt/ui/issues/3353",0.7314164,{"description":2033,"labels":2034,"number":2038,"owner":1985,"repository":2039,"state":1987,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### 🐛 The bug\n\nThe center marker is always show on maps placeholder image.\nSee https://github.com/nuxt/scripts/blob/f96f7b51549f302160559041bbf056589e899b04/src/runtime/components/ScriptGoogleMaps.vue#L394\n\n### 🛠️ To reproduce\n\nttps://stackblitz.com/edit/nuxt-starter-pkwfkx?file=pages%2Findex.vue\n\n### 🌈 Expected behavior\n\nShould be dependent on centerMarker boolean prop: https://github.com/nuxt/scripts/blob/f96f7b51549f302160559041bbf056589e899b04/src/runtime/components/ScriptGoogleMaps.vue#L60\n\n### ℹ️ Additional context\n\n_No response_",[2035],{"name":2036,"color":2037},"bug","d73a4a",402,"scripts","Center marker always shown on maps placeholder image","2025-02-24T14:10:21Z","https://github.com/nuxt/scripts/issues/402",0.7319469,{"description":2045,"labels":2046,"number":2049,"owner":1985,"repository":2050,"state":2051,"title":2052,"updated_at":2053,"url":2054,"score":2055},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2047],{"name":2036,"color":2048},"ff281a",496,"nuxt.com","closed","[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.663974,{"description":2057,"labels":2058,"number":2049,"owner":1985,"repository":2014,"state":2051,"title":2062,"updated_at":2063,"url":2064,"score":2055},"",[2059],{"name":2060,"color":2061},"vitest-environment","b60205","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",{"description":2057,"labels":2066,"number":2069,"owner":1985,"repository":2050,"state":2051,"title":2070,"updated_at":2071,"url":2072,"score":2073},[2067],{"name":1996,"color":2068},"1ad6ff",715,"[Docs] Remove `useScrollToHeading` from TOC","2022-06-30T12:08:37Z","https://github.com/nuxt/nuxt.com/issues/715",0.6655601,{"description":2057,"labels":2075,"number":2076,"owner":1985,"repository":2050,"state":2051,"title":2077,"updated_at":2078,"url":2079,"score":2080},[],996,"[Homepage] Light mode","2022-12-07T06:21:17Z","https://github.com/nuxt/nuxt.com/issues/996",0.6813337,{"description":2082,"labels":2083,"number":2086,"owner":1985,"repository":2002,"state":2051,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.8\n\n### Description\n\n```vue\n\u003Cscript setup lang=\"ts\">\ntype Data = {\n id:number,\n name:string\n}\n\nconst defaultData = [\n {\n id: 1,\n name: \"a\"\n },\n {\n id: 2,\n name: \"b\"\n }\n]\n\nconst data = ref\u003CData[]>([])\nconst rerender = () => {\n if (!data.value?.length) {\n data.value = defaultData\n } else {\n data.value = []\n }\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUButton label=\"rerender\" @click=\"rerender()\" />\n \u003CUTable :data=\"data\">\n \u003Ctemplate #empty>\n no data\n \u003C/template>\n \u003C/UTable>\n \u003C/div>\n\u003C/template>\n\n````\nIn this example, if the table's data is initially empty and then updated (by clicking the \"rerender\" button), you will notice that the content in the empty slot disappears. This indicates that the table's data is no longer empty, yet nothing is rendered in the table. The reason is that the table's columns are not reactive. I believe this limitation is caused by TanStack.\n\n### Potential Solution\n```vue\nwatch(columns, (newColumns) => {\n tableApi.setOptions((prevOpt) => ({\n ...prevOpt,\n columns: newColumns \n }))\n}) \n```\n\n\n\n\n### Additional context\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { watch } from 'vue'\nimport { getCoreRowModel, useVueTable } from '@tanstack/vue-table'\ntype Data = {\n id: number,\n name: string\n}\n\nconst defaultData = [\n {\n id: 1,\n name: \"a\"\n },\n {\n id: 2,\n name: \"b\"\n }\n]\n\nconst data = ref\u003CData[]>([])\nconst columns = computed(() => Object.keys(data.value[0] ?? {}).map((accessorKey: string) => ({ accessorKey, header: accessorKey })))\n\nconst tableApi = useVueTable({\n data,\n columns: columns.value,\n getCoreRowModel: getCoreRowModel()\n})\n\nconst rerender = () => {\n if (!data.value.length) {\n\n data.value = defaultData\n } else {\n data.value = []\n }\n}\n\n/* watch(columns, (newColumns) => {\n tableApi.setOptions((prevOpt) => ({\n ...prevOpt,\n columns: newColumns \n }))\n}) */\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUButton label=\"rerender\" @click=\"rerender()\" />\n \u003Cdiv>\n {{ columns }}\n \u003C/div>\n \u003Cbr>\n \u003Cdiv>\n {{ tableApi.options }}\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n```\n\nnoticed that tableApi's columns won't change along with updates to the data",[2084,2085],{"name":1996,"color":1997},{"name":2024,"color":2025},2689,"[Table] reactive columns for auto-generated UTable columns","2024-11-21T13:11:03Z","https://github.com/nuxt/ui/issues/2689",0.7162568,["Reactive",2092],{},["Set"],["ShallowReactive",2095],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"KtePCHj0T8Vn07sn_z2z2TUhEqzOKpr0PfJrF6_mKd8":-1},"/nuxt/nuxt.com/379"]