\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"triage","ffffff",3583,"nuxt","ui","open","Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.74347657,{"description":2882,"labels":2883,"number":2896,"owner":2874,"repository":2874,"state":2876,"title":2897,"updated_at":2898,"url":2899,"score":2900},"### Describe the feature\n\nI would like to add a footer to my page containing the generation timestamp. However, using `new Date()` does not really work as it is overriden with the current time after hydration. It would be great to have a `\u003CServerOnly>` component analog to the existing `\u003CClientOnly>` component.\r\n\r\nI also tried to put it into `defineAppConfig` which is for \"Public tokens that are determined at build time [...]\" but that still leads to the date being hydrated on the client.\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [X] 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).",[2884,2887,2890,2893],{"name":2885,"color":2886},"enhancement","8DEF37",{"name":2888,"color":2889},"good first issue","fbca04",{"name":2891,"color":2892},"🍰 p2-nice-to-have","0E8A16",{"name":2894,"color":2895},"server components","839413",27073,"`\u003CServerOnly>` component (to render markup only once)","2024-11-05T16:50:37Z","https://github.com/nuxt/nuxt/issues/27073",0.74630153,{"description":2902,"labels":2903,"number":2910,"owner":2874,"repository":2875,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Description\n\nI think the docs havent been updated or this . The docs say to do this to theme components in nuxt config \n\n\n\nbut i get this i think this has been moved\n\n\ni am on version\n\n`3.0.0-alpha.12`",[2904,2907],{"name":2905,"color":2906},"question","d876e3",{"name":2908,"color":2909},"v3","49DCB8",3208,"closed","How To Customize Nuxt Components","2025-01-30T18:42:31Z","https://github.com/nuxt/ui/issues/3208",0.69895804,{"description":2917,"labels":2918,"number":2925,"owner":2874,"repository":2874,"state":2911,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Describe the feature\n\nWhile investigating #26873 i noticed that many of the `_payload.json` files differed only in the last field which contains an integer. Based on the magnitude and value I immediate suspected it might be a valid unix-time and converting it revealed that it seems to be the time when the page was generated.\r\n\r\nI do not know of any reason why these timestamps should exist. Removing them would somewhat automatic file deduplication (though it would still be better if #26873 could be resolved differently - I really like Nuxt but it does not seem feasible to use it for the planned project).\r\nFurthermore the inclusion of the timestamps makes the builds non-reproducible which is another issue that should be resolved.\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).",[2919,2922],{"name":2920,"color":2921},"3.x","29bc7f",{"name":2923,"color":2924},"pending triage","E99695",26881,"Remove timestamp from `_payload.json`","2024-04-23T11:52:31Z","https://github.com/nuxt/nuxt/issues/26881",0.7228914,{"description":2931,"labels":2932,"number":2934,"owner":2874,"repository":2875,"state":2911,"title":2935,"updated_at":2936,"url":2937,"score":2938},"source: https://github.com/tailwindlabs/tailwindcss/pull/13395#issuecomment-2312747557\n\n> [...] in v4, it will be `max-w-[var(--breakpoint-sm)]` as the shorthand arbitrary variable syntax will no longer be supported.\n> \n> `property-[--var-ref]` ➞ `property-[var(--var-ref)]`\n> \n> Related:\n> \n> * [Remove automatic `var(…)` injection #13537](https://github.com/tailwindlabs/tailwindcss/pull/13537)\n> * [Remove automatic `var(…)` injection #13657](https://github.com/tailwindlabs/tailwindcss/pull/13657)\n> * [Disable automatic `var()` injection for anchor properties #13826](https://github.com/tailwindlabs/tailwindcss/pull/13826)\n> \n> [...]",[2933],{"name":2908,"color":2909},2365,"Unsupported Tailwind's shorthand arbitrary variable syntax","2024-10-14T09:02:38Z","https://github.com/nuxt/ui/issues/2365",0.72758853,{"description":2940,"labels":2941,"number":2946,"owner":2874,"repository":2874,"state":2911,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Describe the feature\r\n\r\nsome js,ts files , we want them to work on certain pages or components , global import is not necessary for these files , we want to place these files in the directory where they work .\r\n\r\n```\r\nexport interface layoutItemConfig {\r\n id: string\r\n type: string\r\n positionX: number\r\n positionY: number\r\n spanX: number\r\n spanY: number\r\n maxSpanX?: number\r\n maxSpanY?: number\r\n}\r\n```\r\n\r\nwhen I put this file in `app/pages/gridLayout/types.ts`\r\nIt reminds me `The file app/pages/index/types.ts is not a valid page as it has no content.`\r\n\r\nto make this ERROR not appear , I had to use `export default` or `definePageMeta` in this file\r\ncan we have a configuration item to turn off this check ?\r\n\r\nThere is the reproduction\r\nhttps://stackblitz.com/edit/github-tu5vgq?file=pages%2Findex.vue\r\n\r\nthe error occurred when I started the project\r\n\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,2943],{"name":2923,"color":2924},{"name":2944,"color":2945},"needs reproduction","FBCA04",28410,"Some files in the pages folder do not need to be detected","2024-08-07T10:11:51Z","https://github.com/nuxt/nuxt/issues/28410",0.73835945,{"description":2952,"labels":2953,"number":2954,"owner":2874,"repository":2955,"state":2911,"title":2956,"updated_at":2957,"url":2958,"score":2959},"On the Nuxt Color Module [@nuxtjs/color-mode](https://nuxt.com/modules/color-mode), If you go to the **Release Notes**, see the image below.\r\n\r\n\u003Cimg width=\"1374\" alt=\"image\" src=\"https://github.com/user-attachments/assets/f0dec680-a037-48a2-a352-fa152676922c\">\r\n\r\nWhen you click on the Release Notes link, you are redirected to a [https://color-mode.nuxtjs.org/releases](https://color-mode.nuxtjs.org/releases), which returns a 404 Page Not Found.\r\n\r\n\u003Cimg width=\"962\" alt=\"Screenshot 2024-08-21 at 10 45 00\" src=\"https://github.com/user-attachments/assets/bbd4f629-0653-45d1-b4d6-c9c321185ea2\">",[],1643,"nuxt.com","Broken Link on Nuxt Color Mode in Nuxt module page ","2024-09-11T15:22:16Z","https://github.com/nuxt/nuxt.com/issues/1643",0.7427458,{"description":2961,"labels":2962,"number":2965,"owner":2874,"repository":2875,"state":2911,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\nN/A\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\ncommit: 64b703df8d0a7133a381bfcc7af07644d5d15d4c\n\n### Reproduction\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUSlideover side=\"left\">\n \u003CUButton label=\"Open Slideover\" color=\"neutral\" variant=\"subtle\" />\n \u003Ctemplate #content>\n \u003CUButton label=\"Show toast\" color=\"neutral\" variant=\"outline\" @click=\"showToast\" />\n \u003C/template>\n \u003C/USlideover>\n\n \u003Cbr>\n\n \u003CUModal>\n \u003CUButton label=\"Open Modal\" color=\"neutral\" variant=\"subtle\" />\n \u003Ctemplate #content>\n \u003CUButton label=\"Show toast\" color=\"neutral\" variant=\"outline\" @click=\"showToast\" />\n \u003C/template>\n \u003C/UModal>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst toast = useToast()\n\nfunction showToast() {\n toast.add({\n title: 'Test',\n duration: 60 * 1000\n })\n}\n\u003C/script>\n```\n\n### Description\nFollowing #2404 resolved via b0be26d67feab467ac5862edd82e52df03a5091c\n\nWhile a Slideover or Modal are open trigger a Toaster and try to interact with it.\n\n\nhttps://github.com/user-attachments/assets/945c1f96-7556-42a6-b7e7-f88373b6e38f\n\n",[2963,2964],{"name":2868,"color":2869},{"name":2908,"color":2909},2646,"[v3] Toaster gets rendered behind Slideover's and Modal's overlays","2024-11-15T10:59:18Z","https://github.com/nuxt/ui/issues/2646",0.7463249,{"description":2971,"labels":2972,"number":2978,"owner":2874,"repository":2874,"state":2911,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Describe the feature\n\nIt's a pretty common case to have a dynamic page like `/invoice/\u003CinvoiceId>` and also `/invoice/\u003CinvoiceId>/edit` for editing this invoice. After editing, we want to redirect the user back to `/invoice/\u003CinvoiceId>`, where we are calling `useAsyncData`, of course. However, the result of that call is still returning the cached response from before the edit was done.\r\n\r\nAs I understand it, we can provide a unique key to achieve this:\r\n```ts\r\nconst { data: invoice } = await useAsyncData(\r\n Date.now().toString(),\r\n () => $api.invoices.findOne(company.value.id, invoiceId)\r\n)\r\n```\r\nBut I think it would be convenient to be able to skip the cache entirely with just a simple option:\r\n```ts\r\nconst { data: invoice } = await useAsyncData(\r\n () => $api.invoices.findOne(company.value.id, invoiceId),\r\n { force: true }\r\n)\r\n```\n\n### Additional information\n\n- [ ] 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).",[2973,2974,2977],{"name":2885,"color":2886},{"name":2975,"color":2976},"discussion","538de2",{"name":2920,"color":2921},22608,"Provide convenient option to skip `useAsyncData`'s cache","2023-10-16T21:48:27Z","https://github.com/nuxt/nuxt/issues/22608",0.74634933,{"description":2984,"labels":2985,"number":2989,"owner":2874,"repository":2874,"state":2911,"title":2990,"updated_at":2991,"url":2992,"score":2993},"I've got an issue where I'm setting some data with asyncData, I then update that data, then I change page and the data reverts.\r\n\r\nSo basically I call another function from asyncData in a page component like this:\r\n```js\r\nasyncData (context) {\r\n return ApiPage.getPage(context, context.params.page, 'pages', 'page')\r\n}\r\n```\r\n\r\nThen the file with that function is this (_ApiPage.js):\r\n```js\r\nconst masterData = {\r\n body: '',\r\n form: null,\r\n formData: null,\r\n hasChildren: false,\r\n header: '',\r\n id: '',\r\n label: '',\r\n name: '',\r\n sideMenu: [],\r\n subLabel: '',\r\n subHeader: null\r\n}\r\n\r\nconst AxiosError = function (status, message) {\r\n return {\r\n response: {\r\n status: status,\r\n data: {\r\n message: message\r\n }\r\n }\r\n }\r\n}\r\n\r\nexport default {\r\n mixins: {\r\n methods: {\r\n reloadSideMenu () {\r\n if (this.slug !== '' && this.hasChildren) {\r\n this.$axios.get(this.$store.getters.getApiUrl('menus/home/' + this.slug))\r\n .then((res) => {\r\n this.sideMenu = res.data\r\n })\r\n }\r\n }\r\n }\r\n },\r\n getPage ({ error, store, app }, slug, patchUrlPrefix, cmsKey) {\r\n return app.$axios.get(slug)\r\n .then((res) => {\r\n if (res.statusCode) {\r\n throw new AxiosError(res.statusCode, res.message)\r\n }\r\n if (typeof res.data !== 'object' || !res.data.id) {\r\n throw new AxiosError(404, '')\r\n }\r\n let newData = Object.assign({\r\n slug: slug\r\n }, masterData, res.data)\r\n if (store.getters.getAuthUser() && store.getters.hasRole('ROLE_ADMIN')) {\r\n newData.patchUrl = store.getters.getApiUrl(patchUrlPrefix + '/' + res.data.id)\r\n store.commit('cms/initEndpoint', {\r\n endpoint: newData.patchUrl,\r\n initKey: cmsKey\r\n })\r\n }\r\n // Set whether any further requests are now needed\r\n let loadSideMenu = newData.slug !== '' && newData.hasChildren\r\n let loadForm = newData.form\r\n if (!loadSideMenu && !loadForm) {\r\n return newData\r\n }\r\n // Setup extra requests\r\n let requests = []\r\n let loadPaths = {\r\n form: store.getters.getApiUrl('form/' + slug),\r\n sideMenu: store.getters.getApiUrl('menus/home/' + slug)\r\n }\r\n if (loadForm) {\r\n requests.push(app.$axios.get(loadPaths.form))\r\n }\r\n if (loadSideMenu) {\r\n requests.push(app.$axios.get(loadPaths.sideMenu))\r\n }\r\n // Process sub-requests\r\n return Promise.all(requests)\r\n .then((allRes) => {\r\n for (const res of allRes) {\r\n switch (res.config.url) {\r\n case loadPaths.form:\r\n newData = Object.assign(newData, {\r\n formData: Object.assign(\r\n {},\r\n {\r\n lastModified: res.headers['last-modified']\r\n },\r\n res.data\r\n )\r\n })\r\n break\r\n case loadPaths.sideMenu:\r\n newData = Object.assign(newData, {\r\n sideMenu: res.data\r\n })\r\n break\r\n }\r\n }\r\n return newData\r\n })\r\n .catch((err) => {\r\n error({\r\n statusCode: err.response.status,\r\n message: 'The page\\'s dependencies could not be loaded'\r\n })\r\n })\r\n })\r\n .catch((err) => {\r\n if (err.response) {\r\n error({\r\n statusCode: err.response.status,\r\n message: (err.response.status === 404 ? 'Page could not be found' : err.response.data.message)\r\n })\r\n } else {\r\n if (typeof err === 'string') {\r\n error({\r\n statusCode: 500,\r\n message: err\r\n })\r\n } else {\r\n error({\r\n statusCode: 500,\r\n message: 'An error occurred'\r\n })\r\n }\r\n }\r\n })\r\n }\r\n}\r\n```\r\n\r\nSo I load data and populate `sideMenu`. When I update some pages, the title will affect the URL that needs to be in the menu. So I refresh the menu with the `reloadSideMenu` method - so far so good.\r\n\r\nI then go to another page which using the `_ApiPage.js` file. The sideMenu variable then reverts to the original state that asyncData had set for the page. I've tried logging to the console, and nowhere in my scripts where I set that variable is being reached.\r\n\r\nAny ideas?\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/c996\">#c996\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2986],{"name":2987,"color":2988},"2.x","d4c5f9",1134,"asyncData reverting after data modified","2023-01-18T15:40:52Z","https://github.com/nuxt/nuxt/issues/1134",0.74736434,["Reactive",2995],{},["Set"],["ShallowReactive",2998],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fe8b7Gmp5NehmvCGmoa_BWPM3aoX4w2AntreDL320bho":-1},"/nuxt/nuxt.com/1723"]