\r\n\u003C!-- ... -->\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\" setup>\r\n\r\nconst page = ref\u003Cnumber>(1)\r\n\r\n// temporary name \"promise\" -- maybe this could replace the \"pending\" boolean in Nuxt 4?\r\nconst { data, promise } = useFetch('/api/my-items', {\r\n query: {\r\n page: page\r\n }\r\n})\r\n\r\nasync function handleFetchMore() {\r\n page.value += 1\r\n // would this work? or would nextTick() need to be awaited before it?\r\n await promise.value\r\n}\r\n\r\n// ...\r\n\r\n\u003C/script>\r\n```\r\n\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2879,2882],{"name":2880,"color":2881},"enhancement","8DEF37",{"name":2883,"color":2884},"discussion","538de2",26678,"Return the current promise from `useFetch` in a computed ref","2024-06-30T11:04:44Z","https://github.com/nuxt/nuxt/issues/26678",0.71122885,{"description":2891,"labels":2892,"number":2899,"owner":2869,"repository":2869,"state":2900,"title":2901,"updated_at":2902,"url":2903,"score":2904},"At the moment the documentation uses useLazyFetch (and useFetch with lazy option) without await (https://nuxt.com/docs/getting-started/data-fetching#lazy) as well as with await (https://nuxt.com/docs/api/composables/use-lazy-fetch). Which example is correct? Or is there any difference? But I think it would be good to agree on one way, to avoid confusion.",[2893,2896],{"name":2894,"color":2895},"documentation","5319e7",{"name":2897,"color":2898},"good first issue","fbca04",29931,"closed","Documentation: Consistent examples for useFetchLazy","2024-12-06T20:43:53Z","https://github.com/nuxt/nuxt/issues/29931",0.6855598,{"description":2906,"labels":2907,"number":2910,"owner":2869,"repository":2911,"state":2900,"title":2912,"updated_at":2913,"url":2914,"score":2915},"",[2908],{"name":2880,"color":2909},"1ad6ff",611,"nuxt.com","[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.6924335,{"description":2917,"labels":2918,"number":2910,"owner":2869,"repository":2870,"state":2900,"title":2922,"updated_at":2923,"url":2924,"score":2915},"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```",[2919],{"name":2920,"color":2921},"vitest-environment","b60205","typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2926,"labels":2927,"number":2931,"owner":2869,"repository":2869,"state":2900,"title":2932,"updated_at":2933,"url":2934,"score":2935},"Hi!\r\n\r\nIt is confusing when to use [fetch](https://nuxtjs.org/api/pages-fetch) and when [asyncData](https://nuxtjs.org/api/)\r\n\r\nThey both can:\r\n- access context (store, params)\r\n- both can be called from the server-side\r\n\r\nIf I understand correctly I should use `fetch` when I want to fill the store and `asyncData` when I want to set up component data.\r\n\r\nBut `asyncData` can access store too. So why there are these two methods?\r\n\r\n\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/c1274\">#c1274\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2928],{"name":2929,"color":2930},"2.x","d4c5f9",1432,"Question: difference between fetch and asyncData ","2023-01-18T15:41:50Z","https://github.com/nuxt/nuxt/issues/1432",0.69627905,{"description":2937,"labels":2938,"number":2946,"owner":2869,"repository":2869,"state":2900,"title":2947,"updated_at":2948,"url":2949,"score":2950},"(from various references and nuxt/framework#5738 by @OhB00)\r\n\r\nWe had the ability to force refresh asyncData state using `refresh(true)`. It had been removed in nuxt/framework#699 to make refresh API forward compatible using an object syntax (`{ force: true }`) but also probably reimplement.\r\n\r\nThe main issue with refreshing while another promise is running is that we are not canceling the previous one. (and there is no standard spec for cancelable promises).\r\n\r\nFor useFetch, it is completely doable and we can use cancelation tokens to automatically cancel previous ones.\r\n\r\nFor useAsyncData as handler function that runs promise is black box, we need to find a way to reject stalled promise when it resolved and keep it in an alternative place for asyncDatas.\r\n\r\n",[2939,2940,2943],{"name":2880,"color":2881},{"name":2941,"color":2942},"3.x","29bc7f",{"name":2944,"color":2945},"🍰 p2-nice-to-have","0E8A16",14746,"Force refresh for `useAsyncData` and `useFetch`","2023-01-19T17:39:30Z","https://github.com/nuxt/nuxt/issues/14746",0.6966647,{"description":2952,"labels":2953,"number":2960,"owner":2869,"repository":2961,"state":2900,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.11.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: future, compatibilityDate, modules, css, experimental, runtimeConfig, routeRules, i18n, icon\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxt/image@1.9.0, @nuxtjs/i18n@9.2.0, @vueuse/nuxt@12.5.0\n- Build Modules: -\n------------------------------\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3, latest commit\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/navigation-menu\n\n### Description\n\nThe items (`\u003Cli>`) of NavigationMenu have unnecessary padding top and bottom.\n\nIs:\n\u003Cimg width=\"691\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cdb9a3e5-3429-4883-aa4a-c8e7859356f0\" />\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\" />",[2954,2957],{"name":2955,"color":2956},"bug","d73a4a",{"name":2958,"color":2959},"v3","49DCB8",3328,"ui","NavigationMenu container is too high, creates whitespace","2025-03-28T17:38:47Z","https://github.com/nuxt/ui/issues/3328",0.7029568,{"labels":2967,"number":2971,"owner":2869,"repository":2869,"state":2900,"title":2972,"updated_at":2973,"url":2974,"score":2975},[2968,2969],{"name":2941,"color":2942},{"name":2866,"color":2970},"E99695",14478,"useFetch doesn't respond to state changes, unlike useAsyncData","2023-01-19T17:36:01Z","https://github.com/nuxt/nuxt/issues/14478",0.70465326,{"description":2977,"labels":2978,"number":2979,"owner":2869,"repository":2911,"state":2900,"title":2980,"updated_at":2981,"url":2982,"score":2983},"Use the same component for aside filters on modules and showcase + Add icons on modules\n\n- [x] Merge components\n- [ ] Refactor types\n- [ ] Add icons",[],1149,"[Aside] Use same component","2023-06-06T12:14:41Z","https://github.com/nuxt/nuxt.com/issues/1149",0.70477986,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fsVPnZ_JS7QjahO2cPEbN7KYbZHMK6a9IvhF9JR7yfeI":-1},"/nuxt/nuxt.com/630"]