\n \u003C/NuxtLayout>\n \u003C/UApp>\n\u003C/template>\n\u003Cscript setup lang=\"ts\">\nimport { fr, en } from '@nuxt/ui/locale';\nconst locales = { fr, en };\nconst { t, locale } = useI18n();\n\u003C/script>\n```\nAnalyze your bundle:\n`npx nuxi analyze`\n\n### Description\n\nAs you can see, unused locales are still included in the bundle, while only Fr and En have been imported\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2033,2036],{"name":2034,"color":2035},"bug","d73a4a",{"name":2037,"color":2038},"v3","49DCB8",3602,"ui","i18n, Unused locales are included in the bundle","2025-03-18T14:19:38Z","https://github.com/nuxt/ui/issues/3602",0.66540015,{"labels":2046,"number":2052,"owner":1997,"repository":1997,"state":2010,"title":2053,"updated_at":2054,"url":2055,"score":2056},[2047,2048,2051],{"name":1985,"color":1986},{"name":2049,"color":2050},"discussion","538de2",{"name":2019,"color":2020},14333,"Allow preventing `useFetch`/`useAsyncData` from firing immediately","2023-01-19T17:33:50Z","https://github.com/nuxt/nuxt/issues/14333",0.67751306,{"labels":2058,"number":2061,"owner":1997,"repository":1997,"state":2010,"title":2062,"updated_at":2063,"url":2064,"score":2065},[2059,2060],{"name":2019,"color":2020},{"name":2022,"color":2023},14292,"Respect dynamic params when calling `refresh()` returned by `useFetch`","2023-01-19T17:32:45Z","https://github.com/nuxt/nuxt/issues/14292",0.6775891,{"description":2067,"labels":2068,"number":2071,"owner":1997,"repository":1997,"state":2010,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### Environment\n\nNuxt CLI v3.0.0-rc.8 13:40:47\r\nNuxt project info: 13:40:49\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.6.0`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `build`, `buildModules`, `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `@nuxtjs/tailwindcss@5.3.2`\r\n------------------------------\r\n\n\n### Reproduction\n\ncomponents/ProjectName.vue:\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cspan>\r\n \t{{props.projectId}}\r\n \t\u003Cspan>{{project}}\u003C/span>\r\n \u003C/span>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nconst props = defineProps({\r\n\tprojectId: String\r\n})\r\n\r\nconst projectId = ref(props.projectId)\r\n\r\nconst { data: project, pending, refresh } = await useFetch(\r\n\t() => { \r\n\t\tconst url = '/api/projects/' + projectId.value; \r\n\t\tconsole.log(url);\r\n\t\treturn url\r\n\t}, {\r\n\t headers: useRequestHeaders(['cookie']),\r\n\t watch: [projectId],\r\n\t lazy: false,\r\n\t cache: false\r\n\t})\r\n\r\n\u003C/script>\r\n```\r\n\r\n\r\npages/[projectId].vue\r\n\r\n```\r\n\u003Ctemplate>\r\n\u003CProjectName :projectId=$route.params.projectId />\r\n\u003C/template>\r\n```\n\n### Describe the bug\n\nIf \"projectId\" prop of the ProjectName.vue component changes, the useFetch url() generation function is called and writes the new url via console.log(url) to console. However, no new data is fetched from the backend.\n\n### Additional context\n\nMight be related to https://github.com/nuxt/nuxt.js/issues/14462 \n\n### Logs\n\n_No response_",[2069,2070],{"name":2019,"color":2020},{"name":2022,"color":2023},14770,"useFetch with url function does not re-fetch data","2023-01-19T17:40:02Z","https://github.com/nuxt/nuxt/issues/14770",0.68151444,{"description":2077,"labels":2078,"number":2082,"owner":1997,"repository":1997,"state":2010,"title":2083,"updated_at":2084,"url":2085,"score":2086},"I have 3 level of nesting in my pages (subject/topic/subtopic/content). If a user navigates in correct sequence i.e starting from subject to content, all data is fetched on page change and everything works well.\r\n\r\nBut If a user refreshes the browser on content or subtopic page, how do I fetch all the previous data ? I am using fetch method to get data for each page, should I use fetch to get data for all the previous pages ? How do I do it? I am using vuex store, so every data fetch is written in actions of vuex.\r\n\r\nHow do I avoid fetching the duplicate data when client doesn't refresh the page but simply navigate from client side page to another page?\r\n\r\nAny help will be highly appreciated.\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/c1647\">#c1647\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2079],{"name":2080,"color":2081},"2.x","d4c5f9",1833,"Fetch from multiple api's on page refresh using fetch method","2023-01-18T15:42:45Z","https://github.com/nuxt/nuxt/issues/1833",0.6841416,{"description":2088,"labels":2089,"number":2092,"owner":1997,"repository":1997,"state":2010,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### Environment\n\nNuxt project info: 12:16:19\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.8.1\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.2\r\n- Package Manager: pnpm@8.6.12\r\n- Builder: -\r\n- User Config: devtools, nitro\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-k5ugr3?file=pages%2Fabout.vue\n\n### Describe the bug\n\ntwo ways to give a param to useFetch\r\n\r\n1. give a pure string\r\n2. give a computed vary\r\n\r\ntwo way to go into \"about\" page\r\n1. click about link in home\r\n2. in about page and refresh to reload\r\n\r\nwhen get about page from other page by route, both useFetch get correct data\r\n\r\nwhen refresh the about page, a pure string param will get a real data immidiate, but a ref make it null.\r\n\r\nboth useFetch will get data finally if just render in template or shown somewhere, But if the code below rely on the data to make a special logic, it need to always need a watch \"pending\" to run the logic later, it's a bug or a design?\r\n\r\nthis will get null data in client console\r\n```\r\nconst { data } = await useFetch('/api/user', { query: { param1: id } });\r\n```\r\nthis get the correct data\r\n```\r\nconst { data } = await useFetch('/api/user', { query: { param1: id.value } });\r\n```\r\n\r\n// null or [1,2,3]\r\n// the log in ssr server console is always right.\r\nconsole.log('data', data.value);\n\n### Additional context\n\nNo, just run the reproduction\n\n### Logs\n\n```shell-script\nserver logs is correct. client logs get null\n```\n",[2090,2091],{"name":2019,"color":2020},{"name":2022,"color":2023},24300,"useFetch data is null in some case depending on the query param type.","2023-11-15T19:40:57Z","https://github.com/nuxt/nuxt/issues/24300",0.6848792,{"description":2098,"labels":2099,"number":2102,"owner":1997,"repository":1997,"state":2010,"title":2103,"updated_at":2104,"url":2105,"score":2106},"### Describe the feature\r\n\r\nThe cache for the data fetching mechanism is already accessible via `useNuxtApp().payload.data`, I'm suggesting exposing it with a separate composable (`useNuxtData` or `getNuxtData`). it can introduce some interesting data-fetching patterns such as optimistic updates.\r\n\r\n### Examples\r\n- Showing stale data instead of a loading spinner (reading from cache): \r\n\r\n```ts\r\ninterface Post {\r\n userId: number;\r\n title: string;\r\n body: string;\r\n id: number\r\n}\r\n\r\nconst id = useRoute().params.id\r\n\r\nconst { data } = useLazyFetch(`/api/post/${id}`, {\r\n key: `post-${id}`,\r\n server: false,\r\n default: () => {\r\n return (useNuxtData().posts as Post[]).find(d => d.id === +id)\r\n }\r\n})\r\n```\r\n\r\n- Update the UI while the query is being invalidated in the background (writing to cache): \r\n\r\n```ts\r\n// in List.vue\r\nconst { data } = useLazyFetch('/api/notes', {\r\n key: 'notes'\r\n})\r\n\r\n// In Form.vue\r\nconst text = ref('')\r\n\r\nconst add = () => {\r\n (useNuxtData().notes as string[]).push(text.value)\r\n // ... Some mutation\r\n refreshNuxtData('notes')\r\n}\r\n```\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [X] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2100,2101],{"name":2019,"color":2020},{"name":2022,"color":2023},15582,"Accessing async data cache object with a new composable","2023-01-19T17:56:33Z","https://github.com/nuxt/nuxt/issues/15582",0.6850048,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"jqVsyklLNTipMP1jCdqzBgBtG0JJ-hgFklbKAW50AYg":-1},"/nuxt/ui/3868"]