`;\r\n\r\n maps.value.createAdvancedMapMarker({\r\n position: marker.position,\r\n content: markerContent.firstChild as Node,\r\n }).then((mapMarker: any) => {\r\n mapMarker.setMap(maps.value.map);\r\n // console.log('Marker added:', mapMarker.map);\r\n }).catch((error: any) => {\r\n console.error('Error adding marker:', error);\r\n });\r\n });\r\n}\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CScriptGoogleMaps v-if=\"isLoaded\" ref=\"maps\" class=\"map-container\" @ready=\"handleReady\"\r\n :mapOptions=\"mapOptions\">\r\n \u003C/ScriptGoogleMaps>\r\n\u003C/template>\r\n\r\n\r\nThanks for your help!\r\n\r\n\r\n### 🔍 Where should you find it?\r\n\r\nThis is the only thing I have found on the [docs](https://scripts.nuxt.com/scripts/content/google-maps#advanced-marker-control)(Guide section) but it is quite vage.\r\n\r\n### ℹ️ Additional context\r\n\r\n_No response_",[3045],{"name":3046,"color":3047},"documentation","0075ca",244,"closed","Google Maps: Custom Markers (AdvancedMapMarker)","2025-02-14T11:11:36Z","https://github.com/nuxt/scripts/issues/244",0.45961785,{"description":3055,"labels":3056,"number":1338,"owner":3024,"repository":3024,"state":3049,"title":3065,"updated_at":3066,"url":3067,"score":3068},"Hi, I think a lot of issues faced by Next.js apply to Nuxt.js also, and I believe that ultimately, such a feature will require a way to allow for custom server workflows, with session support etc.\r\nInterested to discuss this.\r\n\r\nhttps://github.com/zeit/next.js/issues/153\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/c12\">#c12\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3057,3059,3062],{"name":3046,"color":3058},"5319e7",{"name":3060,"color":3061},"3.x","29bc7f",{"name":3063,"color":3064},"2.x","d4c5f9","Add login / authentication example","2023-01-19T14:23:45Z","https://github.com/nuxt/nuxt/issues/4",0.71512216,{"description":3070,"labels":3071,"number":3072,"owner":3024,"repository":3073,"state":3049,"title":3074,"updated_at":3075,"url":3076,"score":3077},"This css blocks the render of page... Why not this resource with async and defer?\r\n\r\n\r\n",[],155,"icon","Render blocking CSS WPO Core Vitals","2024-07-18T22:45:44Z","https://github.com/nuxt/icon/issues/155",0.74955934,{"description":3079,"labels":3080,"number":3088,"owner":3024,"repository":3089,"state":3049,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Environment\n\n(CodeSandbox) \n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future\n- Runtime Modules: @nuxt/ui@3.0.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/quirky-pare-zxxn6x\n\n### Description\n\nThe RadioGroup component does not accept boolean values, despite the documentation saying it should. I'm not sure if this is a bug or is intended and the documentation is wrong.\n\nIn the provided codesandbox (using v3.0.2) you can see the type errors in the code, as well as buggy behavior in the app.\n\nDocs: https://github.com/nuxt/ui/blob/9ec159e20793a0f7346ad4ec9c0fe142320f0fa2/docs/content/3.components/radio-group.md?plain=1#L20\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3081,3082,3085],{"name":3035,"color":3036},{"name":3083,"color":3084},"v3","49DCB8",{"name":3086,"color":3087},"triage","ffffff",3724,"ui","RadioGroup does not accept booleans","2025-04-03T10:21:37Z","https://github.com/nuxt/ui/issues/3724",0.7551715,{"description":3095,"labels":3096,"number":3098,"owner":3024,"repository":3089,"state":3049,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v22.3.0`\r\n- Nuxt Version: `3.13.1`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `yarn@1.22.22`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`, `modules`, `plugins`, `runtimeConfig`, `i18n`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxtjs/i18n@8.5.1`\r\n- Build Modules: `-`\r\n\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts\n\n### Description\n\n## Description\r\nThe Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:\r\n\r\nThe notification component occupies part of the screen unnecessarily.\r\nIt overlaps other elements on the page due to its z-index, potentially disrupting the user interface.\r\n\r\n## Expected Behavior\r\nThe notification component should only be created and added to the DOM when a toast is actually triggered.\r\n\r\n## Current Behavior\r\nThe notification component is always present in the DOM, regardless of whether a toast has been triggered or not.\r\n\r\n## Steps to Reproduce\r\n\r\n- Implement the Nuxt UI notification component in a project.\r\n- Inspect the DOM without triggering any toasts.\r\n- Observe that the notification component is present and has a z-index applied.\r\n\r\n## Additional Context\r\nThis issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.\r\n\r\n## Possible Solution\r\nConsider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).\r\n\u003Cimg width=\"1427\" alt=\"Screenshot 2024-09-04 at 6 29 00 PM\" src=\"https://github.com/user-attachments/assets/da90352f-71e6-4aaf-9bda-7a9e4a3fd056\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3097],{"name":3035,"color":3036},2113,"Notification component created even when toast is not triggered, causing z-index issues","2024-11-09T10:24:37Z","https://github.com/nuxt/ui/issues/2113",0.7554418,{"description":3104,"labels":3105,"number":3110,"owner":3024,"repository":3089,"state":3049,"title":3111,"updated_at":3112,"url":3113,"score":3114},"### Environment\n\n### Description\n\nThe `ID` column is not displayed when it is the first element in the columns array and item selection is enabled in the NuxtUI table.\n\n``` js\nconst columns = [\n {\n key: 'id',\n label: 'ID',\n },\n {\n key: 'displayName',\n label: 'Display Name',\n },\n {\n key: 'email',\n label: 'Email',\n }\n]\n```\n\n\n\n### Expected Behavior\n\nThe `ID` column should be displayed correctly regardless of its position in the columns array.\n\n### Workaround\n\nAdding a placeholder column before the `ID` column resolves the issue temporarily.\n\n```js\nconst columns = [\n {\n key: 'placeholder',\n },\n```\n\n\n\n\n### Environment\n\n- NuxtUI Version: 2.20.0\n- Browser: Chrome\n- Operating System: Windows 11\n\n### Version\n\n2.20.0\n\n### Reproduction\n\n### Steps to Reproduce\n\n1. Create a table with item selection enabled.\n2. Set a `ID` column as the first element in the columns array.\n3. Observe that the `ID` column is not displayed.\n",[3106,3107],{"name":3035,"color":3036},{"name":3108,"color":3109},"duplicate","cfd3d7",3040,"Columns [0] Element Does not Display if the Table is Selectable","2025-01-08T10:01:01Z","https://github.com/nuxt/ui/issues/3040",0.7607588,{"description":3116,"labels":3117,"number":3123,"owner":3024,"repository":3089,"state":3049,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.9.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.0\n- Nitro Version: 2.11.8\n- Package Manager: bun@1.2.8\n- Builder: -\n- User Config: compatibilityDate, devtools, future, runtimeConfig, modules, css, app, ui, icon, fonts, image, nitro\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxt/image@1.10.0, @nuxt/scripts@0.11.5, nitro-cloudflare-dev@0.2.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.2\n\n### Reproduction\n\n*\n\n### Description\n\ncomponent\n```vue\n\u003CUAvatar\n src=\"https://example.com/image.ong\"\n class=\"size-12 shrink-0 translate-y-5\"\n/>\n```\n\nnuxt.config.ts\n```ts [nuxt.config.ts]\nimage: {\n provider: \"aliyun\",\n format: [\"webp\", \"png\"],\n densities: [1],\n },\n```\n\nPreview image\n\u003Cimg width=\"991\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cd3afe88-5bd0-4db8-813c-629c8831c946\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3118,3119,3120],{"name":3035,"color":3036},{"name":3083,"color":3084},{"name":3121,"color":3122},"upstream","78bddb",3763,"Configuring @nuxt/image in Nuxt causes Avatar to incorrectly construct external image URLs","2025-04-11T12:41:20Z","https://github.com/nuxt/ui/issues/3763",0.76423204,{"labels":3129,"number":3134,"owner":3024,"repository":3024,"state":3049,"title":3135,"updated_at":3136,"url":3137,"score":3138},[3130,3133],{"name":3131,"color":3132},"pending triage","E99695",{"name":3063,"color":3064},7349,"Docker compose can't bind the servers ip-address rather it's bind dockers inet address","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7349",0.76505876,["Reactive",3140],{},["Set"],["ShallowReactive",3143],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQME8puB5Mxk0IT2AayMdzJoY93U_CEkvNkkxQ_2l-SY":-1},"/nuxt/icon/244"]