\n\nShould:\n\u003Cimg width=\"694\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/155b8a32-2e58-44b0-becf-7646c39e40f7\" />\n\nOtherwise this leads to unexpected whitespaces. E.g. the following has class `mt-0` but still shows a significant margin:\n\u003Cimg width=\"316\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/af76a978-85cd-4ed4-9269-8dfca3c9686d\" />\n\n### Additional context\n\nTabs doesnt have this:\n\u003Cimg width=\"1040\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f5849972-7c7b-421a-9f9c-03d0a73f5572\" />",[2901,2904],{"name":2902,"color":2903},"bug","d73a4a",{"name":2905,"color":2906},"v3","49DCB8",3328,"ui","closed","NavigationMenu container is too high, creates whitespace","2025-03-28T17:38:47Z","https://github.com/nuxt/ui/issues/3328",0.697276,{"description":2915,"labels":2916,"number":2920,"owner":2869,"repository":2921,"state":2909,"title":2922,"updated_at":2923,"url":2924,"score":2925},"We should discuss what to show in that video, maybe a teasing video for the moment ?",[2917],{"name":2918,"color":2919},"design","00bd6f",630,"nuxt.com","[Projects] Video","2022-10-03T11:03:26Z","https://github.com/nuxt/nuxt.com/issues/630",0.7165627,{"description":2927,"labels":2928,"number":2934,"owner":2869,"repository":2869,"state":2909,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\r\n\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.3.2`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `modules`, `css`, `build`, `vite`, `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\nSee this [StackBlitz](https://stackblitz.com/edit/nuxt-starter-nrkwmz?file=pages/a.vue)\r\n\r\n### Describe the bug\r\n\r\nI understand `useAsyncData` to behave like `useState` but it can be initialized with an async function instead. (based on this discussion #17654). However, in my test it seems that `useAsyncState` is always reinitialized and not sharing the state.\r\n\r\nWhen I have two pages A and B which shall display the same state (for example a timestamp created at the state's initialization) I can use `useState` like this to get the desired effect, and navigating between the two pages does not reinitialize the state.\r\n```js\r\nexport const useTime = () => useState('time', () => (new Date()).getTime())\r\n```\r\n\r\nHowever, when using an async intialization function with `useAsyncData` the state is reinitialized with a new timestamp after navigating to the other page.\r\n```js\r\nexport const useTime = () => useAsyncData('time', async () => {\r\n await new Promise((resolve) => {\r\n setTimeout(() => resolve('resolved'), 1000)\r\n })\r\n return new Date().getTime()\r\n})\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2929,2932],{"name":2930,"color":2931},"3.x","29bc7f",{"name":2866,"color":2933},"E99695",19972,"`useAsyncData` does not share state","2023-03-29T10:12:09Z","https://github.com/nuxt/nuxt/issues/19972",0.72021776,{"description":2940,"labels":2941,"number":2951,"owner":2869,"repository":2869,"state":2909,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the feature\r\n\r\nThe `useState` uses `useNuxtApp().payload.state` to preserve the value after server-side rendering and share the value across all components through a unique key. If `useState` is previously used with a key and if the key is the same, it will use the cached value regardless of whether it has a different `init` method or not. It is useful to use cached data when needed. However, in some cases, the value of `useState` needs to be redeclared with a new `init` method. It seems like the only way is creating unique key every time.\r\n\r\nIt would be nice to have just like `clearNuxtData` function to clear cached state value, so we don't have to think how to make a unique key when we want to change the value of `useState`\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2942,2944,2947,2948],{"name":2888,"color":2943},"8DEF37",{"name":2945,"color":2946},"good first issue","fbca04",{"name":2930,"color":2931},{"name":2949,"color":2950},"🍰 p2-nice-to-have","0E8A16",21293,"Provide `clearNuxtState` function for `useState`","2023-06-09T21:22:23Z","https://github.com/nuxt/nuxt/issues/21293",0.7212972,{"description":2957,"labels":2958,"number":2961,"owner":2869,"repository":2921,"state":2909,"title":2962,"updated_at":2963,"url":2964,"score":2965},"",[2959],{"name":2888,"color":2960},"1ad6ff",611,"[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.73503053,{"description":2967,"labels":2968,"number":2961,"owner":2869,"repository":2870,"state":2909,"title":2970,"updated_at":2971,"url":2972,"score":2965},"I'm on v0.11.2 and it seems what `defineVitestConfig` wants and the type definition doesn't line up?\r\n\r\nIt wants an `InlineConfig` passed in directly in the typedef, but I'm having to do this:\r\n\r\n```js\r\nimport { defineVitestConfig } from \"nuxt-vitest/config\";\r\nimport type { InlineConfig } from \"vitest\";\r\n\r\nconst test: InlineConfig = {\r\n coverage: {\r\n all: true,\r\n branches: 87.5, // 7 / 8\r\n exclude: [\r\n \"node_modules\",\r\n \".nuxt\",\r\n \"app\",\r\n \"dist\",\r\n \"scripts\",\r\n \"*.config.ts\",\r\n \"**/types.ts\",\r\n \"**/*.tests.ts\",\r\n \"**/*.js\",\r\n \"**/*.mjs\",\r\n \"pages\",\r\n \"plugins\",\r\n \"app.vue\",\r\n ],\r\n },\r\n environment: \"happy-dom\",\r\n include: [\"**/*.tests.ts\"],\r\n};\r\n\r\n// eslint-disable-next-line @typescript-eslint/ban-ts-comment\r\n// @ts-ignore\r\nexport default defineVitestConfig({ test });\r\n```",[2969],{"name":2891,"color":2892},"typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2974,"labels":2975,"number":2978,"owner":2869,"repository":2869,"state":2909,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Environment\n\nMy pc:\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.1.0`\r\n- Nitro Version: `2.0.0`\r\n- Package Manager: `yarn@1.22.15`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\nAlso happens in stackblitz:\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.1.0`\r\n- Nitro Version: `2.0.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: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-zrc5sy?file=components/StateGetter.vue\r\n\r\nIn this example there are two components that set the state, and one that reads the state.\r\nThe only difference between the setters is that useState is called after the awaited function in `StateSetterAfterAwait.vue` and before the awaited function in `StateSetterBeforeAwait.vue`.\r\n\r\nNotice that the `console.log` in `StateSetterAfterAwait.vue` is never reached, nor is the state set.\n\n### Describe the bug\n\nWhen `useState` is called after an awaited function in `useAsyncData`, execution halts.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2976,2977],{"name":2930,"color":2931},{"name":2866,"color":2933},18568,"Execution halts when useState is used after awaited function in useAsyncData","2023-03-02T08:32:26Z","https://github.com/nuxt/nuxt/issues/18568",0.7354792,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f908A4lgaOiu3sXNpCnNzlCViP-_Mzix3jhxX475N_Gw":-1},"/nuxt/test-utils/480"]