\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle scoped>\n /* Optional styling */\n\u003C/style>\n\n\u003Cstyle scoped>\n /* Ensure map has full width and fixed height */\n #map {\n width: 100%;\n height: 16rem; /* 64 Tailwind units */\n }\n\u003C/style>\n\n\n```\n\n\n\n\n### 🔍 What have you tried?\n\n_No response_\n\n### ℹ️ Additional context\n\n_No response_",[1984],{"name":1985,"color":1986},"help wanted","008672",314,"nuxt","scripts","open","Centermarker disappears when loading active googlemap","2024-11-10T17:33:02Z","https://github.com/nuxt/scripts/issues/314",0.7355203,{"description":1996,"labels":1997,"number":1987,"owner":1988,"repository":2001,"state":1990,"title":2002,"updated_at":2003,"url":2004,"score":1994},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-framework-zehqm6\n\n### Describe the bug\n\nThe empty `await setup({})` in the tests takes ~4 seconds for every rerun in `watch` mode in the empty project.\r\nPlease, check the reproduction, try to run `npm test`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[1998],{"name":1999,"color":2000},"enhancement","a2eeef","test-utils","The \"setup\" in the tests is very slow for every rerun","2024-12-03T16:02:16Z","https://github.com/nuxt/test-utils/issues/314",{"description":2006,"labels":2007,"number":2008,"owner":1988,"repository":2009,"state":1990,"title":2010,"updated_at":2011,"url":2012,"score":2013},"I added @nuxt/icon to my project. In the project it is working fine but in histoire it is not working.\r\nIn histoire it is not able to render the stories that contain components that use @nuxt/icon.\r\n\r\nOn devtools console you always see the error:\r\n\u003Cimg width=\"654\" alt=\"Bildschirmfoto 2024-07-22 um 21 10 24\" src=\"https://github.com/user-attachments/assets/4793e76d-e549-4712-bdfc-dc230c1cb56f\">\r\n\r\nit doesn't matter if mode is css or svg, it doesn't matter if from iconify icon libs, global components or custom collections, it is simple not able to work with it. The error is always the same.\r\n\r\nHere is a reproduction: https://stackblitz.com/edit/nuxt-starter-kckxy8\r\nrun the histoire to see the story not getting rendered and the console error in devtools.\r\n\r\nPlease help!",[],212,"icon","@nuxt/icon not working in histoire with mode \"svg\"","2024-08-11T05:45:02Z","https://github.com/nuxt/icon/issues/212",0.7373369,{"description":2015,"labels":2016,"number":2023,"owner":1988,"repository":2024,"state":1990,"title":2025,"updated_at":2026,"url":2027,"score":2028},"### Description\n\nhi\nafter i upgrade from v2 to v3 i get this error : \n\n[plugin:vite:vue] [@vue/compiler-sfc] Failed to resolve extends base type.\nIf this previously worked in 3.2, you can instruct the compiler to ignore this extend by adding /* @vue-ignore */ before it, for example:\n\ninterface Props extends /* @vue-ignore */ Base {}\n\nNote: both in 3.2 or with the ignore, the properties in the base type are treated as fallthrough attrs at runtime.\n\n/node_modules/@nuxt/ui/dist/runtime/components/Carousel.vue\n151| const appConfig = useAppConfig()\n152| const { dir, t } = useLocale()\n153| const rootProps = useForwardProps(reactivePick(props, 'active', 'align', 'breakpoints', 'containScroll', 'dragFree', 'dragThreshold', 'duration', 'inViewThreshold', 'loop', 'skipSnaps', 'slidesToScroll', 'startIndex', 'watchDrag', 'watchResize', 'watchSlides', 'watchFocus'))\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n154| \n155| const prevIcon = computed(() => props.prevIcon || (dir.value === 'rtl' ? appConfig.ui.icons.arrowRight : appConfig.ui.icons.arrowLeft))\n\n\ncan anyone help me ?",[2017,2020],{"name":2018,"color":2019},"question","d876e3",{"name":2021,"color":2022},"v3","49DCB8",3873,"ui","[@vue/compiler-sfc] Failed to resolve extends base type.","2025-04-13T06:59:01Z","https://github.com/nuxt/ui/issues/3873",0.74009246,{"description":2030,"labels":2031,"number":2032,"owner":1988,"repository":2033,"state":1990,"title":2034,"updated_at":2035,"url":2036,"score":2037},"\r\n\u003Cimg width=\"1229\" alt=\"image\" src=\"https://github.com/nuxt/nuxt.com/assets/73933669/a8b6473a-c737-4783-ad7f-148b07f0bf56\">\r\n\r\nhttps://github.com/nuxt/nuxt.com/assets/73933669/747e1528-e1b6-4c89-ae63-4afc0d74e471\r\n\r\n\r\nBrowser: Safari (i think this issue might be on every browser)\r\n\r\nHow to reproduce:\r\nSpam `cmd + r` if you're on windows `ctrl + r`.",[],1582,"nuxt.com","Cannot load payload ~ A bug maybe","2024-05-15T07:13:12Z","https://github.com/nuxt/nuxt.com/issues/1582",0.750063,{"description":2039,"labels":2040,"number":2048,"owner":1988,"repository":2024,"state":1990,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Reproduction\n\n````\n\u003Ctemplate>\n \u003CUChip text=\"test\" size=\"3xl\">\n \u003CUButton icon=\"i-lucide-mail\" color=\"neutral\" variant=\"subtle\" />\n \u003C/UChip>\n\u003C/template>\n````\n\n### Description\n\nHey,\n\nThanks for your great work.\n\nI have noticed this on a few elements in UI3, but especaily here padding just is not right. Yes of course you can change it, but i belive there needs to be some sane defaults across all elements.\n\nText in chip, and even a simple number is almost unreadable see screenshot below. Happy to open a pr or list all other elements where this seems to have happened (one that comes to mind is UAvatar https://github.com/nuxt/ui/issues/3558).\n\n\n\n### Additional context\n\nThis example is directly from the UI website",[2041,2044,2045],{"name":2042,"color":2043},"bug","d73a4a",{"name":2021,"color":2022},{"name":2046,"color":2047},"triage","ffffff",3633,"Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.75570554,{"description":2054,"labels":2055,"number":2059,"owner":1988,"repository":2001,"state":2060,"title":2061,"updated_at":2062,"url":2063,"score":2064},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: ../../packages/package-one/src/module, ../../packages/package-two/src/module\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nYou get the error when using vitest 2.1.8 (the error appears since 2.1.5): https://stackblitz.com/edit/github-n797ja-hxhseq\n\nIt works in 2.1.4: https://stackblitz.com/edit/github-n797ja-2rtuvw\n\n### Describe the bug\n\nIn a workspace with multiple projects, it is no longer possible to call defineVitestConfig because of unctx conflicts:\n\n```\nError: Context conflict\n at checkConflict (file:///home/projects/github-n797ja-hxhseq/node_modules/unctx/dist/index.mjs:25:13)\n at set (file:///home/projects/github-n797ja-hxhseq/node_modules/unctx/dist/index.mjs:59:22)\n at initNuxt (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4404:21)\n at ready (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4306:26)\n at loadNuxt (file:///home/projects/github-n797ja-hxhseq/node_modules/nuxt/dist/index.mjs:4871:16)\n```\n\nCould be related to https://github.com/nuxt/test-utils/issues/537\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2056],{"name":2057,"color":2058},"pending triage","5D08F5",1034,"closed","Can't load config files in workspace since vitest 2.1.5","2025-02-11T15:38:57Z","https://github.com/nuxt/test-utils/issues/1034",0.4632165,{"description":2066,"labels":2067,"number":2072,"owner":1988,"repository":1989,"state":2060,"title":2073,"updated_at":2074,"url":2075,"score":2076},"Upgrading to v6.0.2 I get the following errors in the Nuxt Turnstile module:\r\n\r\n```\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleTagManager' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleAnalytics' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n```\r\n\r\nhttps://github.com/nuxt-modules/turnstile/actions/runs/9820960416/job/27116095724?pr=321#step:14:24",[2068,2069],{"name":2042,"color":2043},{"name":2070,"color":2071},"pre-announce","c2e0c6",133,"fix(tpc): a type annotation is necessary","2024-07-15T18:18:26Z","https://github.com/nuxt/scripts/issues/133",0.71153295,{"description":2078,"labels":2079,"number":2082,"owner":1988,"repository":2033,"state":2060,"title":2083,"updated_at":2084,"url":2085,"score":2086},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_05_23_at_16_23_53_7945ec0dde.mp4\n",[2080],{"name":2042,"color":2081},"ff281a",555,"[Nuxt3] Children pages reloads on first query param change","2022-11-17T11:45:24Z","https://github.com/nuxt/nuxt.com/issues/555",0.7321591,{"description":2088,"labels":2089,"number":2082,"owner":1988,"repository":2001,"state":2060,"title":2093,"updated_at":2094,"url":2095,"score":2086},"I have some components that include \"client\" components (i.e. ClientComponent.client.vue). When I run tests for components that include client components, they always seem to fail with messages like this:\r\n\r\n```\r\n[Vue warn]: Component \u003CAnonymous>: setup function returned a promise, but no \u003CSuspense> boundary was found in the parent component tree. A component with async setup() must be nested in a \u003CSuspense> in order to be rendered. \r\n at \u003CClientComponent.client> \r\n at \u003CTestA ref=\"VTU_COMPONENT\" > \r\n at \u003CVTUROOT>\r\n```\r\n\r\nA simple component that I'm testing looks like this:\r\n\r\n\r\n```\r\n// TestA.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CClientComponent />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nand the test file looks like this:\r\n\r\n\r\n```\r\n// TestA.spec.ts\r\nimport { describe, it, expect } from 'vitest';\r\nimport { mount } from '@vue/test-utils';\r\nimport TestA from './TestA.vue';\r\n\r\ndescribe('Competition TestA', () => {\r\n it('renders component', async () => {\r\n const wrapper = mount(TestA);\r\n expect(wrapper.text()).toContain('Client component here...');\r\n });\r\n});\r\n\r\n```\r\n\r\nFinally, the client component:\r\n\r\n```\r\n// ClientComponent.client.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>Client component here...\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nIf I remove the \".client\" from the component file name (to make it just ClientComponent.vue), then the tests will run and pass normally. However, there are some cases where I want to use \".client\" to make sure it's only rendered client-side.\r\n\r\n### Reproduction \r\nhttps://stackblitz.com/edit/github-ndby6m?file=components/TestA.spec.ts\r\n\r\nFailures can be seen there by running `pnpm run test`",[2090],{"name":2091,"color":2092},"vitest-environment","b60205","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",["Reactive",2097],{},["Set"],["ShallowReactive",2100],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"RBRs1-UIjlpBDdd0KC79NGbGRoIw4AVufSTW0uQR69g":-1},"/nuxt/nuxt.com/1034"]