\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_",[3148],{"name":3149,"color":3150},"help wanted","008672",314,"scripts","Centermarker disappears when loading active googlemap","2024-11-10T17:33:02Z","https://github.com/nuxt/scripts/issues/314",0.7501108,{"description":3158,"labels":3159,"number":3151,"owner":3138,"repository":3163,"state":3140,"title":3164,"updated_at":3165,"url":3166,"score":3156},"### 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_",[3160],{"name":3161,"color":3162},"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":3168,"labels":3169,"number":3173,"owner":3138,"repository":3163,"state":3174,"title":3175,"updated_at":3176,"url":3177,"score":3178},"I'm getting the following errors\r\n\r\n```\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: Environment \"nuxt\" is not a valid environment. \r\n```\r\n\r\nthis happens on `vitest ` version > 0.34 \r\nno errors with vitest 0.33\r\n\r\n\r\n```\r\nimport { defineVitestConfig } from 'nuxt-vitest/config';\r\n\r\nexport default defineVitestConfig({\r\n test: {\r\n environment: 'nuxt',\r\n },\r\n});\r\n\r\n\r\n```",[3170],{"name":3171,"color":3172},"vitest-environment","b60205",520,"closed"," Vitest 0.34 error - Environment \"nuxt\" is not a valid environment","2023-12-02T00:37:17Z","https://github.com/nuxt/test-utils/issues/520",0.6979277,{"description":3180,"labels":3181,"number":3182,"owner":3138,"repository":3139,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"\r\n\r\n",[],1438,"[Support] Workshops & Trainings link directs to HTTP 404","2023-12-04T11:28:56Z","https://github.com/nuxt/nuxt.com/issues/1438",0.7320513,{"description":3188,"labels":3189,"number":3199,"owner":3138,"repository":3200,"state":3174,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Environment\n\n System:\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\n Memory: 44.48 GB / 62.57 GB\n Container: Yes\n Shell: 5.9 - /usr/bin/zsh\n Browsers:\n Chrome: 126.0.6478.126\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/select-menu\n\n### Description\n\n1. open docs\n2. open any select menu\n3. select any option\n4. tab to next field\n5. tab index is reset\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3190,3193,3196],{"name":3191,"color":3192},"bug","d73a4a",{"name":3194,"color":3195},"v3","49DCB8",{"name":3197,"color":3198},"reka-ui","56d799",2350,"ui","[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.7342121,{"description":3206,"labels":3207,"number":3210,"owner":3138,"repository":3139,"state":3174,"title":3211,"updated_at":3212,"url":3213,"score":3214},"Modules and Showcases are missing in mobile nav, presumably since migration from .md to Nuxt pages",[3208],{"name":3191,"color":3209},"ff281a",993,"[Code] Add missing links in mobile nav","2022-12-07T06:20:26Z","https://github.com/nuxt/nuxt.com/issues/993",0.73794276,{"description":3216,"labels":3217,"number":3220,"owner":3138,"repository":3139,"state":3174,"title":3221,"updated_at":3222,"url":3223,"score":3224},"\n\nThe select should be after the input text",[3218],{"name":3161,"color":3219},"1ad6ff",547,"[Project] Invert type and input on YAML fields","2022-05-23T15:16:52Z","https://github.com/nuxt/nuxt.com/issues/547",0.747949,{"description":3226,"labels":3227,"number":3220,"owner":3138,"repository":3163,"state":3174,"title":3229,"updated_at":3230,"url":3231,"score":3224},"I've have run into use case that seems peculiar, but I wanted to pose it here in case it's something that would make sense to bundle into this package as an enhancement.\r\n\r\nPut simply, I needed to do something like `registerEndpoint`, but to be able to set it up _before the Nuxt app starts_. We've tried calling `registerEndpoint` as early as possible, but from what I've seen, this just mocks calls for once the Vue app is mounted to the window, not before.\r\n\r\nWhat I've landed on as a solution is have a Nuxt plugin that's only included for test runs which replaces the global `$fetch` with a mock implementation of `$fetch` wrapped in `vi.fn()`, plus a mock implementation of `$fetch.create`. That's coupled with an object that can be configured with the return values like so:\r\n\r\n```ts\r\nconst endpointMocks = {\r\n 'http://0.0.0.0:8000/api/1.0': {\r\n some: {\r\n endpoint: () => ({ ok: true }),\r\n },\r\n },\r\n};\r\n```\r\n\r\nRight now it catches any call that doesn't match a path in this object, and raises an error instead of making a request.\r\n\r\nIs this a feature that would be desirable to be included as part of `nuxt-vitest`? Or perhaps would this be better suited as its own module/package elsewhere?",[3228],{"name":3171,"color":3172},"enhancement: mocking $fetch before app starts (@sidebase/nuxt-auth)","2023-12-02T23:39:53Z","https://github.com/nuxt/test-utils/issues/547",{"description":3233,"labels":3234,"number":3235,"owner":3138,"repository":3163,"state":3174,"title":3236,"updated_at":3237,"url":3238,"score":3239},"Originally reported by nuxt/test-utils#329, when having multiple `.test` files, jest runs them in parallel. If two depending on a single fixture and need build, this causes issues. Some options are:\r\n\r\n- Using run-in-band to disable parallel run\r\n- Using a lock-file so one test awaits on others during build\r\n- Using random build ids for `buildDir`\r\n- Using mfs (#49) for building in mem (considering all internals can support)\r\n\r\n",[],413,"fix: build conflict between multiple tests","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/413",0.7485883,["Reactive",3241],{},["Set"],["ShallowReactive",3244],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbvLCLcRuP4r1UEGmz8ybRLu0DZ-ntSx_4ZqAx5Cuq8s":-1},"/nuxt/nuxt.com/1448"]