\r\n \u003C/template>\r\n \u003Ctemplate #option=\"{ option: search }\">\r\n \u003CNuxtLink to=\"test\">\r\n\r\n \u003Ch4 class=\"truncate p-2 font-semibold\">{{ search.name }}\u003C/h4>\r\n \u003C/NuxtLink>\r\n \u003C/template>\r\n \u003C/UInputMenu>\r\n \r\n \r\n \r\n async function search(q: string): Promise\u003CEsAutoSuggestion[]> {\r\n if (q == null) {\r\n return [];\r\n }\r\n loading.value = true;\r\n const searchSuggestions = await searchStore.searchAutoSuggestion(q)\r\n if (!searchSuggestions) {\r\n loading.value = false;\r\n return []\r\n }\r\n loading.value = false;\r\n \r\n return searchSuggestions ?? []\r\n }",[2921,2924,2927],{"name":2922,"color":2923},"question","d876e3",{"name":2925,"color":2926},"wontfix-v2","ffffff",{"name":2928,"color":2929},"v3","49DCB8",2058,"ui","How to Open a `uiMenu` in `UInputMenu` on Focus","2024-10-18T14:10:19Z","https://github.com/nuxt/ui/issues/2058",0.78003544,{"description":2937,"labels":2938,"number":2946,"owner":2874,"repository":2874,"state":2913,"title":2947,"updated_at":2948,"url":2949,"score":2950},"Adding unit tests for `generateRoutesFromFiles` to test route generation patterns",[2939,2940,2943],{"name":2901,"color":2902},{"name":2941,"color":2942},"pages","00DFB5",{"name":2944,"color":2945},"test","1DB6E0",11757,"unit tests for pages","2023-01-19T15:42:34Z","https://github.com/nuxt/nuxt/issues/11757",0.7803549,{"description":2952,"labels":2953,"number":2960,"owner":2874,"repository":2874,"state":2913,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### What problem does this feature solve?\n\nThis solves the issue where some e2e test runners depend on the site being fully loaded when starting tests. Currently the site shows as loaded to the test framework which causes testing to prematurely start and fail.\n\n### What does the proposed changes look like?\n\nI propose to add a CLI flag to disable the loading screen for testing purposes.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9450\">#c9450\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2954,2955,2957],{"name":2868,"color":2896},{"name":2922,"color":2956},"cc317c",{"name":2958,"color":2959},"2.x","d4c5f9",6025,"Add option to disable the loading screen","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/6025",0.78240883,{"description":2966,"labels":2967,"number":2970,"owner":2874,"repository":2874,"state":2913,"title":2971,"updated_at":2972,"url":2973,"score":2974},"Currently under `the` `render` section of `nuxt.config.js` there is an option `resourceHints` (boolean), which enabled (default) or disabled (by setting to `false`) which, based on the documentation:\r\n\r\n> Adds prefetch and preload links for faster initial page load time.\r\n\r\nI have a rather large list of routes, and some routes that are only used by users that have certain roles/privileges.\r\n\r\nIt would be nice if:\r\n\r\n- `prefetch` could be disabled, while still having `preload` (for things like the common chunks) enabled.\r\n- Set a flag in the pages (similar to how `scrollToTop` is flagged), to enable/disble `preload` or, `prefetch`. for that particular page component\r\n- Specify chunknames (or grouping) for a set of routes (i.e. via the page component definition) to group several small pages into the same webpackChunkName file\r\n\r\n\r\n99% of the my users cannot access `administrative` pages, so it is kind of a waste of b/w to pre-fetch those pages which will never be loaded by those users, without having to disable site-wide pre-fetching (which affects 100% of the users)\r\n\r\nAn other option would be able to group pre-fetches by a user speified parameter... say if someone accesses /admin (and isn't re-directed/blocked by middleware), then all the child routes of `/admin would be listed/added in the head as prefetch links.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1652\">#c1652\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2968,2969],{"name":2868,"color":2896},{"name":2958,"color":2959},1838,"Changing prefetch and preload options (resourceHints)","2023-01-18T15:42:45Z","https://github.com/nuxt/nuxt/issues/1838",0.78247845,{"description":2976,"labels":2977,"number":2994,"owner":2874,"repository":2874,"state":2913,"title":2995,"updated_at":2996,"url":2997,"score":2998},"### Describe the feature\n\nCurrently, we send back all states (`useState`) from island within the island response.\r\n\r\nIt currently doesn't have any impact on the app calling the island.\r\n\r\nThere's 2 solutions:\r\n- we keep it and fix the bug where the state isn't applied to the current App\r\n - ⚠️What would happen if we have 2 island located in the same component ? Both are making a promise so the user cannot know what will happen (in which order useState will be set)\r\n- we completly remove it and reduce the json payload for island responses.\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).",[2978,2981,2982,2985,2988,2991],{"name":2979,"color":2980},"good first issue","fbca04",{"name":2901,"color":2902},{"name":2983,"color":2984},"bug","d73a4a",{"name":2986,"color":2987},"🔨 p3-minor","FBCA04",{"name":2989,"color":2990},"performance","E84B77",{"name":2992,"color":2993},"server components","839413",26579,"Remove or fix `state` from islands components","2024-04-20T01:56:58Z","https://github.com/nuxt/nuxt/issues/26579",0.78388065,{"labels":3000,"number":3007,"owner":2874,"repository":2874,"state":2913,"title":3008,"updated_at":3009,"url":3010,"score":3011},[3001,3002,3003,3004],{"name":2901,"color":2902},{"name":2983,"color":2984},{"name":2944,"color":2945},{"name":3005,"color":3006},"❗ p4-important","D93F0B",13394,"Vitest was initialized with native Node instead of Vite Node","2023-01-19T17:48:01Z","https://github.com/nuxt/nuxt/issues/13394",0.7845891,{"description":3013,"labels":3014,"number":3016,"owner":2874,"repository":2874,"state":2913,"title":3017,"updated_at":3018,"url":3019,"score":3020},"Followup https://github.com/nuxt/framework/pull/8890 by @danielroe\r\n\r\nThere are currently some uncertain decisions about the final API and behavior with payload extraction behavior like how we apply payload updates on CSR route change (should the key of static payload be prefixed with routes as well or remain global same as asyncData keys). (Tracker issue: nuxt/nuxt.js#14507)\r\n\r\nMaking the decision to enable this feature or not is a tricky one because on one hand, we are really close to v3.0.0 release deadline and we don't want to mark a functionality as stable and change it in a semver-minor release and on the other hand, payload extraction is an essential feature for the release with full static generation support.\r\n\r\nI suggest two behaviors:\r\n\r\n- For `nuxt build` when we have a server and the possibility of having hybrid prerendering, disable an option by default. **Payload extraction will be always opt-in in Nuxt 3 for server mode**.\r\n - Docs: Deploy>Node.js Server https://v3.nuxtjs.org/getting-started/deployment#nodejs-server\r\n- For `nuxt generate` when we are expected to output a \"full static\" output, enable the future\r\n - Update the docs and warn about the stability of `nuxt generate` \r\n - Explain how payload extraction works and what are consequences of disabling it (needing a server)\r\n - Docs: Deploy> Static Hosting https://v3.nuxtjs.org/getting-started/deployment#static-hosting\r\n\r\nAn alternative is to always disable feature until we are really sure it is stable but there are few downsides:\r\n- Enabling it by default for `nuxt generate`, even if super stable, is still a breaking change considering we essentially change caching strategy\r\n- Enabling it with a new flag (nuxt2 was `target: 'static'`) is less intuitive for starter users and even more confusing to explain\r\n- Differing to enable, means also less usage of the feature and harder to ever stabilize it\r\n\r\n",[3015],{"name":2901,"color":2902},15450,"Disable payload extraction for `nuxi build`","2023-01-19T17:50:38Z","https://github.com/nuxt/nuxt/issues/15450",0.7867543,["Reactive",3022],{},["Set"],["ShallowReactive",3025],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKhc69oNBAmFSMU5nrzf0LiKt6IeybdeJFdMaWA8cDzk":-1},"/nuxt/ui/3905"]