\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[1995,1998],{"name":1996,"color":1997},"bug","d73a4a",{"name":1999,"color":2000},"triage","ffffff",2713,"ui","UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.78275067,{"description":2008,"labels":2009,"number":2013,"owner":1985,"repository":2014,"state":2015,"title":2016,"updated_at":2017,"url":2018,"score":2019},"To give feedback back to Anthony.",[2010],{"name":2011,"color":2012},"enhancement","1ad6ff",840,"nuxt.com","closed","Beta test Nuxt Devtools","2022-08-01T14:27:56Z","https://github.com/nuxt/nuxt.com/issues/840",0.617099,{"description":2021,"labels":2022,"number":2026,"owner":1985,"repository":2027,"state":2015,"title":2028,"updated_at":2029,"url":2030,"score":2031},"## Steps to reproduce\r\n\r\nRun tests including the JSDOM ones: `pnpm test`\r\nThe following tests are failing:\r\n```\r\n × can use $fetch\r\n × can mock fetch requests 5014ms\r\n```\r\n\r\n## Triage\r\n\r\nThis seems to be a compatibility issue coming from the `Headers` implementation in `node-fetch`. This is discussed further [here](https://github.com/node-fetch/node-fetch/issues/1119).\r\n\r\nJSDOM uses the package [whatwg-url](https://github.com/jsdom/whatwg-url) which has a standard compliant implementation of `URLSearchParams`. When `node-fetch` (incorrectly) implements `Headers` using `URLSearchParams` from `whatwg-url` we get the error seen in the tests.\r\n\r\nI'm assuming Happy-DOM has an implementaiton of `URLSearchParams` that is less strict, and thus we do not get these errors there.\r\n\r\nIt also seems like [this line](https://github.com/danielroe/nuxt-vitest/blob/main/packages/vitest-environment-nuxt/src/index.ts#L64) is not working as intended since `globalThis.fetch` is `undefined` even in Node 18. Probably there is some isolation going on in Vitest that is preventing us from accessing the Node global.\r\n",[2023],{"name":2024,"color":2025},"vitest-environment","b60205",530,"test-utils","fetch does not work when using JSDOM","2023-12-02T00:32:10Z","https://github.com/nuxt/test-utils/issues/530",0.67475,{"description":2033,"labels":2034,"number":2040,"owner":1985,"repository":2002,"state":2015,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.1\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.42\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/i18n@9.1.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nV3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-forked-gxx7qs\n\n### Description\n\nWhen using a USelectMenu together with the placeholder or label-key it collides with the slots. The rendered elements are overlapping. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2035,2036,2039],{"name":1996,"color":1997},{"name":2037,"color":2038},"v3","49DCB8",{"name":1999,"color":2000},3022,"USelectMenu placeholder/selected value collides with slots","2025-04-08T10:26:50Z","https://github.com/nuxt/ui/issues/3022",0.71928036,{"description":2046,"labels":2047,"number":2050,"owner":1985,"repository":2014,"state":2015,"title":2051,"updated_at":2052,"url":2053,"score":2054},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2023_01_23_at_15_11_43_212c437f80.mp4\n",[2048],{"name":1996,"color":2049},"ff281a",1179,"[Nav]: Fix exact link route","2023-02-15T12:31:14Z","https://github.com/nuxt/nuxt.com/issues/1179",0.7252245,{"description":2056,"labels":2057,"number":2061,"owner":1985,"repository":2027,"state":2015,"title":2062,"updated_at":2063,"url":2064,"score":2065},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.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: npm@10.2.3\r\n- Builder: -\r\n- User Config: modules, devtools\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\n\n### Reproduction\n\n[Minimal reproduction](https://stackblitz.com/edit/github-ftohct?file=app.nuxt.test.ts)\n\n### Describe the bug\n\nHi all! Do I understand correctly that on the current version of `@nuxt/test-utils` there is no way to pre-fill a store using this instruction from the [Pinia](https://pinia.vuejs.org/cookbook/testing.html#Initial-State) documentation.\r\n\r\n```\r\nimport { describe, test, expect, vi } from 'vitest';\r\nimport { createTestingPinia } from '@pinia/testing';\r\nimport { mountSuspended } from '@nuxt/test-utils/runtime';\r\nimport App from './app.vue';\r\n\r\nconst siteInfoMock = {\r\n title: 'Nuxt 3',\r\n url: 'https://nuxt.com',\r\n};\r\n\r\ndescribe('App link', async () => {\r\n const wrapper = await mountSuspended(App, {\r\n global: {\r\n plugins: [\r\n createTestingPinia({\r\n initialState: {\r\n Site: {\r\n siteInfo: siteInfoMock,\r\n },\r\n },\r\n createSpy: vi.fn,\r\n }),\r\n ],\r\n },\r\n });\r\n\r\n test('Should render the link with a substitute title', () => {\r\n expect(wrapper.get('[data-test-id=\"link\"]').text()).toBe(\r\n siteInfoMock.title\r\n );\r\n\r\n // The test passes because the data in the \"Site\" store has not been changed.\r\n // expect(wrapper.get('[data-test-id=\"link\"]').text()).toBe('Example.com');\r\n });\r\n\r\n test('Should render the link with the spoofed link', () => {\r\n expect(wrapper.get('[data-test-id=\"link\"]').attributes().href).toBe(\r\n siteInfoMock.url\r\n );\r\n\r\n // The test passes because the data in the \"Site\" store has not been changed.\r\n // expect(wrapper.get('[data-test-id=\"link\"]').attributes().href).toBe('https://example.com');\r\n });\r\n});\r\n```\r\nThe component is also rendered, receiving default data from the store. In turn, I expect replacement data in the store.\r\n\r\nI tried to look for information about a similar case in local chats and here in different threads, but I just didn’t receive any information. Several users have raised a similar issue.\r\n\r\n* https://discordapp.com/channels/473401852243869706/1199858451833168004/1199858605831241820\r\n* https://discordapp.com/channels/473401852243869706/496371343542059011/1195669478403489862\r\n* https://discordapp.com/channels/473401852243869706/496371343542059011/1153407426087886942\r\n\r\nIt seems like `@pinia/nuxt` & `@nuxt/test-utils` are not fully compatible, namely the `createTestingPinia` & `mountSuspended` methods.\r\n\r\nPlease tell me, someone was able to solve the problem of how to create a test instance of Pinia.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nstdout | createSuspenseBoundary (/home/projects/rlmilwjxk.github/node_modules/.pnpm/@vue+runtime-core@3.4.15/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1439:43)\r\n\u003CSuspense> is an experimental feature and its API will likely change.\r\n\r\nstderr | warn$1 (/home/projects/rlmilwjxk.github/node_modules/.pnpm/@vue+runtime-core@3.4.15/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:46:13)\r\n[Vue warn]: App already provides property with key \"Symbol(pinia)\". It will be overwritten with the new value.\n```\n",[2058],{"name":2059,"color":2060},"pending triage","5D08F5",737,"mountSuspended & createTestingPinia","2024-11-28T08:58:33Z","https://github.com/nuxt/test-utils/issues/737",0.7599315,{"description":2067,"labels":2068,"number":2069,"owner":1985,"repository":2014,"state":2015,"title":2070,"updated_at":2071,"url":2072,"score":2073},"Pages ready for review:\n\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/modules (searchbar will be updated today)\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/modules/tailwindcss (single module page)\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/showcase\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/partners/agencies\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/partners/agencies/ship-shape (single agency page)\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/partners/sponsors\n- [ ] https://nuxt-com-git-main-nuxtlabs.vercel.app/partners/jobs",[],998,"[Design] Acceptance testing","2023-10-10T14:45:26Z","https://github.com/nuxt/nuxt.com/issues/998",0.7661919,{"description":2075,"labels":2076,"number":2077,"owner":1985,"repository":2078,"state":2015,"title":2079,"updated_at":2080,"url":2081,"score":2082},"@harlan-zw hi!\r\n\r\nI may have missed it somewhere, although I've gone through the documentation completely.\r\nCan you please tell me if it is possible to add two or more GTM containers?\r\nIf so, how do I use them?\r\n\r\nIn brief - I need to use different gtm-id on different url's. And the GTM script should be loaded immediately, by default",[],154,"scripts","Two or more GTM containers","2024-08-07T02:22:06Z","https://github.com/nuxt/scripts/issues/154",0.7696877,{"description":2084,"labels":2085,"number":2088,"owner":1985,"repository":2002,"state":2015,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.2\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, sitemap, linkChecker, modules, supabase, image, routeRules, feed, robots, schemaOrg\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxtjs/supabase@1.4.6, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0, @nuxthub/core@0.8.15, @nuxtjs/sitemap@7.2.4, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.2, nuxt-schema-org@4.1.1, nuxt-link-checker@4.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nSorry for not providing a reproduction, but here it is on your doc website:\n\nhttps://github.com/user-attachments/assets/66177383-ee49-4a89-8083-19e8e96f8be4\n\nIn the screen capture you can see:\n1. I click a button, grant it focus\n2. scroll up\n3. open the search modal with command palette using `meta + k`\n4. close the modal\n5. I am immediately scrolled to the last focused element\n\n### Description\n\nAs shown in the screen cap in the reproduction section, closing the modal returns focus to the last focused element causing you to scroll to its position.\n\nI realize this is an accessibility feature, but being abruptly scrolled down is confusing and jarring for users.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2086,2087],{"name":1996,"color":1997},{"name":2037,"color":2038},3227,"Closing modal causes abrupt scrolling to last focused element","2025-02-18T10:01:47Z","https://github.com/nuxt/ui/issues/3227",0.7728495,["Reactive",2094],{},["Set"],["ShallowReactive",2097],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"zQSdGKLT7xEY6LSeSc-sAmliiZexWpZEujqZl6cd8sM":-1},"/nuxt/nuxt.com/762"]