\u003C/Suspense>',\r\n})\r\n\r\nconst wrapper = render(TestComponent, {\r\n global: {},\r\n})\r\ndescribe(`[${TestComponent.__name}]`, () => {\r\n test('正常系', () => {\r\n expect(true).toBe(true)\r\n })\r\n})\r\n```",[3158,3161],{"name":3159,"color":3160},"vitest-environment","b60205",{"name":3162,"color":3163},"needs reproduction","DE7793",562,"test-utils","closed","TypeError: Invalid URL","2023-12-02T22:52:43Z","https://github.com/nuxt/test-utils/issues/562",0.47140595,{"description":3172,"labels":3173,"number":3177,"owner":3149,"repository":3178,"state":3166,"title":3179,"updated_at":3180,"url":3181,"score":3182},"",[3174],{"name":3175,"color":3176},"enhancement","1ad6ff",359,"nuxt.com","Fetch components from project url `/api/component-meta`","2022-04-19T13:51:35Z","https://github.com/nuxt/nuxt.com/issues/359",0.64929694,{"description":3184,"labels":3185,"number":3177,"owner":3149,"repository":3165,"state":3166,"title":3186,"updated_at":3187,"url":3188,"score":3182},"Update e2e section to use `@nuxt/test-utils`\r\n\r\nhttps://nuxtjs.org/guide/development-tools#end-to-end-testing",[],"update e2e section in nuxtjs.org","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/359",{"description":3190,"labels":3191,"number":3192,"owner":3149,"repository":3178,"state":3166,"title":3193,"updated_at":3194,"url":3195,"score":3196},"Fetch project components from API\n\nBlocked by #167 ",[],165,"Pass components as props in `DocusEditor`","2022-04-21T12:50:26Z","https://github.com/nuxt/nuxt.com/issues/165",0.71916944,{"description":3198,"labels":3199,"number":3192,"owner":3149,"repository":3200,"state":3166,"title":3201,"updated_at":3202,"url":3203,"score":3196},"Script can be found [here](https://help.ads.microsoft.com/#apex/ads/en/56686/2-500)\r\n\r\nI attempted to implement it myself like below, but I am running into problems with UET not being available from the script that is being set, since it is part of the script being loaded.\r\n```ts\r\nconst { uetq, $script } = useRegistryScript('bing', () => ({\r\n scriptInput: {\r\n src: 'https://bat.bing.com/bat.js',\r\n async: true,\r\n crossorigin: false,\r\n },\r\n scriptOptions: {\r\n use() {\r\n return { uetq: window.uetq }\r\n },\r\n },\r\n clientInit: import.meta.server\r\n ? undefined\r\n : () => {\r\n window.uetq = window.uetq || []\r\n\r\n const options = { ti: 'YOUR_KEY_HERE', enableAutoSpaTracking: true }\r\n // @ts-expect-error untyped\r\n options.queue = window.uetq\r\n // @ts-expect-error untyped\r\n window.uetq = new UET(options)\r\n\r\n window.uetq.push('consent', 'default', { ad_storage: 'denied' })\r\n },\r\n}))\r\n```\r\n\r\nThe original script creates a brand new script element with `https://bat.bing.com/bat.js` as the source and then sets the window.uetq from there, but I am unsure how to recreate that in a registry script.",[],"scripts","Add Microsoft UET to registry","2024-09-03T16:09:41Z","https://github.com/nuxt/scripts/issues/165",{"description":3205,"labels":3206,"number":3214,"owner":3149,"repository":3149,"state":3166,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Environment\n\nNuxt 3.2.0\n\n### Reproduction\n\nnuxt.config 👍 \r\n```js\r\nrouteRules: {\r\n // see https://nuxt.com/docs/guide/concepts/rendering#route-rules\r\n '/api/**': {\r\n // enable CORS\r\n cors: true,\r\n }\r\n}\r\n```\r\n\n\n### Describe the bug\n\naccording to MDN CORS spec, header should be :\r\nhttps://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Methods\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3207,3210,3211],{"name":3208,"color":3209},"3.x","29bc7f",{"name":3140,"color":3141},{"name":3212,"color":3213},"upstream","E8A36D",19057,"wrong CORS header access-control-allowed-methods should be access-control-allow-methods","2023-02-15T17:10:35Z","https://github.com/nuxt/nuxt/issues/19057",0.7364045,{"description":3220,"labels":3221,"number":3231,"owner":3149,"repository":3149,"state":3166,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Versions\r\n\r\n- v2.14.6\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/s/crazy-browser-fw1wo?file=/components/ArchiveFetcher.vue\r\n\r\n### Steps to reproduce\r\n\r\n``` \r\ndata() {\r\n return {\r\n fetchedPosts: [],\r\n };\r\n },\r\n components: {\r\n //CountriesList,\r\n CountriesList: () => import(\"~/components/CountriesList\"),\r\n },\r\n async fetch() {\r\n if (process.server) {\r\n let url = \"https://jsonplaceholder.typicode.com/posts\";\r\n console.warn(url, \"Archive fetching\");\r\n try {\r\n this.fetchedPosts = await this.$axios.$get(url);\r\n } catch (err) {\r\n return this.$nuxt.error({ statusCode: 404, message: err.message });\r\n }\r\n console.log(this.fetchedPosts); - return array of posts\r\n }\r\n },\r\n mounted() {\r\n console.warn(this.fetchedPosts); - return [];\r\n }, \r\n```\r\n\r\nAsync import component and try to use it with server-side data.\r\n\r\n### What is Expected?\r\nExpected the same behavior as default components import, without remounting\\refetching on the client.\r\n\r\n### What is actually happening?\r\nWhen we use such construction (async components import) - the component is filling with data on the server-side, but then it looks like remounting on the client without any data and trying to fetch it again.\r\nWhen I import a component in the default way, it works as expected, without losing data on the client.\r\n\r\nI hope I describe the issue clearly enough, but let me know if you need any additional info.",[3222,3225,3228],{"name":3223,"color":3224},"stale","ffffff",{"name":3226,"color":3227},"pending triage","E99695",{"name":3229,"color":3230},"2.x","d4c5f9",8513,"Component remounting and refetching data on client side in case of usage async components import","2023-01-22T15:38:24Z","https://github.com/nuxt/nuxt/issues/8513",0.7372538,{"description":3237,"labels":3238,"number":3240,"owner":3149,"repository":3149,"state":3166,"title":3241,"updated_at":3242,"url":3243,"score":3244},"I am not sure if it explicitly the purpose of the project to provide components that are either always client-side rendered or both server and client-side (universal); however, is it possible to render components or pages completely on the server and avoid client-side hydration?\r\n\r\nThe main use case is that I want to tap into a REST API to generate the data that will shape the components. The issue that I am running into is that I am running into CORS issues on the client side and I believe that I am possibly exposing credentials into the front end. \r\n\r\nThe REST API that I am using relies on credentials and I would prefer if I can manage this completely with the middleware and Vue stores; however, if I try to go this route and try to make the components only grab the data if the context is on the server, I get console errors reporting that there are differences between the client and server rendered components.\r\n\r\nIf the ability to render the components only on the server side was possible, I think Nuxt would be an even more better platform. I think it would be a killer use case in that you can have single file components with the light use of javascript as needed. I could also avoid DOM interactions completely.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7344\">#c7344\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3239],{"name":3229,"color":3230},3509,"Is it possible to have components/pages that are rendered on the server ONLY","2023-01-18T16:24:10Z","https://github.com/nuxt/nuxt/issues/3509",0.74627614,{"description":3246,"labels":3247,"number":3253,"owner":3149,"repository":3149,"state":3166,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.10.1`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `yarn@1.22.21`\r\n- Builder: `-`\r\n- User Config: `devtools`, `app`, `experimental`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\nflags:\r\n`{ experimental: { componentIslands: { selectiveClient: true } }`\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/marccremer/nuxt_islands_issue\n\n### Describe the bug\n\nWhen you rerender a server component it doesnt work on the inner client components.\r\nIn the example you change the props by clicking on the button.\r\nYou expect \"heyfalse\" to turn into \"heytrue\".\r\nNothing happens\n\n### Additional context\n\nThe given example works when you remove the baseUrl.\r\nIt seems that on rererend er the dynmic import doesnt take the baseUrl.\r\nIt should be `import(\"http://localhost:3000\"+baseUrl+\"component.vue\")`\r\nBut it does instead this\r\n`import(\"http://localhost:3000\"+\"component.vue\")`\r\nAnd doesnt find the import.\r\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: Failed to fetch dynamically imported module: http://localhost:3000/_nuxt/@fs/home/redacted/nuxt_island_issue/components/ClientShow.vue?import\n```\n",[3248,3249,3250],{"name":3208,"color":3209},{"name":3226,"color":3227},{"name":3251,"color":3252},"server components","839413",25676,"Client component within server component not working, when app.baseUrl is set","2024-03-15T16:16:42Z","https://github.com/nuxt/nuxt/issues/25676",0.7473272,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEKcBIw6WvDIHKm49E_3FOcmxI5T4nOlbC2-BwQ8oymE":-1},"/nuxt/nuxt.com/562"]