\u003C!-- it's server component: ContentView.server.vue -->\r\n\u003C/template>\r\n\r\n```\r\n\r\n_/src/components/content/ContentView.server.vue_\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\ndefineProps\u003C{ text: string }>()\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Carticle class=\"content\">\r\n \u003Cdiv v-html=\"text\">\u003C/div>\r\n \u003C/article>\r\n\u003C/template>\r\n\r\n```\r\n\r\n_server side: /server/api/news/[id].get.ts_\r\n\r\n```ts\r\nexport default defineEventHandler(async (event) => {\r\n try {\r\n return {\r\n text: 'Lorem ipsum dolor sit amet......', // For simple reproduce, it's enough to pass a text of approximately 50k chars. \r\n // ....other fields\r\n }\r\n } catch (error) {\r\n throw createError({ statusCode: 404, message: 'Material not found' })\r\n }\r\n})\r\n\r\n```\n\n### Describe the bug\n\nI've a ContentView component that accepts article content from the API server, which I pass to v-html. \r\nMy task is to render ContentView **ONLY** on the server side. For this, I added the **server** suffix to component (ContentView.**server**.vue).\r\n\r\nbut the problem is that a lot of data is passed to the ContentView component into props. \r\n```vue\r\n\u003CContentView v-bind=\"data\" /> \u003C!-- DATA with a large amount of data information -->\r\n```\r\nand that's why I get error \"431 Request Header Fields Too Large\".\r\n\r\nMy browser request:\r\n```\r\nRequest URL: http://localhost:3000/__nuxt_island/ContentView_KqN6hVg9ec.json?props=%7B%22text%22:%22Lorem+ipsum+dolor+sit+amet...... 50k chars\r\nRequest Method: GET\r\nStatus Code: 431 Request Header Fields Too Large\r\nRemote Address: [::1]:3000\r\n```\r\n\r\nThis probably not be a bug, but I need to do the component render only on the server side. Please any solutions.\r\n\r\nOr, so that the request to ISLAND is not GET.\r\n\r\nThank you!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2048],{"name":2028,"color":2029},28567,"Nuxt3 .server (island) components fail to render \"Request Header Fields Too Large\" if you pass a lot of data to props","2024-08-16T14:11:40Z","https://github.com/nuxt/nuxt/issues/28567",0.6908302,{"description":2055,"labels":2056,"number":2062,"owner":1988,"repository":1988,"state":1989,"title":2002,"updated_at":2063,"url":2064,"score":2065},"### Environment\n\nDev\n\n### Reproduction\n\nNo reproduction.\n\n### Describe the bug\n\nGetting the below error after updating my nuxt version from ('^3.5.1') to ('^3.11.1).\r\nand it will break the page and show \"This page isn't working\", after reloding it work's fine.\r\n\r\nError is here.\r\n```\r\nbrowser.mjs?v=fd19e36f:44 Uncaught (in promise) RangeError: Maximum call stack size exceeded\r\n at BrowserReporter.log (browser.mjs?v=fd19e36f:44:7)\r\n at Consola._log (core.mjs?v=fd19e36f:381:16)\r\n at resolveLog (core.mjs?v=fd19e36f:349:14)\r\n at Consola._logFn (core.mjs?v=fd19e36f:377:5)\r\n at core.mjs?v=fd19e36f:306:19\r\n at BrowserReporter.log (browser.mjs?v=fd19e36f:44:7)\r\n at Consola._log (core.mjs?v=fd19e36f:381:16)\r\n at resolveLog (core.mjs?v=fd19e36f:349:14)\r\n at Consola._logFn (core.mjs?v=fd19e36f:377:5)\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2057,2060,2061],{"name":2058,"color":2059},"3.x","29bc7f",{"name":2028,"color":2029},{"name":2010,"color":2011},26605,"2024-04-17T15:24:02Z","https://github.com/nuxt/nuxt/issues/26605",0.6924797,{"description":2067,"labels":2068,"number":2074,"owner":1988,"repository":1988,"state":1989,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Version\r\n\r\n[v1.4.2](https://github.com/nuxt.js/releases/tag/v1.4.2)\r\n\r\n### Reproduction link\r\n\r\n[https://github.com/uptownhr/nuxt-issue-3914](https://github.com/uptownhr/nuxt-issue-3914)\r\n\r\n### Steps to reproduce\r\n\r\n1. clone repo\r\n2. yarn\r\n3. yarn build\r\n4. yarn start\r\n5. ab -c 2 -n 20000\r\n\r\nThe STR is not straight forward as I'm only able to reproduce this on a live project I have and running `ab -c 2 -n 20000`. It's only once the server has been hit around 10k times where the bug `Maximum Stack` on `VueComponent.mergeDataFn` is triggered. \r\n\r\nOnce this error is triggered, I can see on the log `statusCode: 500`, however the web server still responds with 200 and shows an error page.\r\n\r\n\r\n```\r\n{ RangeError: Maximum call stack size exceeded\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1164:34)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51)\r\nwww_1 | at VueComponent.mergedDataFn (/www/node_modules/vue/dist/vue.runtime.common.js:1166:51) statusCode: 500, name: 'RangeError' }\r\n```\r\n\r\n\r\n### What is expected ?\r\n\r\nWhen the SSR rendering crashes, the web response should also be a 500. \r\n\r\nSecond thing that should probably is happen is also kill the server, so the process manager has a chance to reboot the server.\r\n\r\n### What is actually happening?\r\n\r\nThe server errors and still returns a 200. This causes error monitors not be able to alert. Also because it catches the crash and not actually crash, any process managers listening to restart the server cannot. \r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7771\">#c7771\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2069,2072,2073],{"name":2070,"color":2071},"stale","ffffff",{"name":2028,"color":2029},{"name":1985,"color":1986},3914,"Nuxt SSR crashes with 200 response code","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3914",0.69901603,{"description":2080,"labels":2081,"number":2095,"owner":1988,"repository":1988,"state":1989,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.3.1`\r\n- Nitro Version: `2.3.1`\r\n- Package Manager: `npm@9.5.0`\r\n- Builder: `vite`\r\n- User Config: `modules`, `imports`, `runtimeConfig`, `typescript`, `app`, `nitro`\r\n- Runtime Modules: `@nuxt/devtools@0.2.5`, `@nuxtjs/robots@3.0.0`, `@nuxtjs/tailwindcss@6.6.0`, `@pinia/nuxt@0.4.7`, `@vueuse/nuxt@9.13.0`, `nuxt-icons@3.1.0`, `nuxt-vitest@0.6.8`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nOn a large project small project does not have this problem\n\n### Describe the bug\n\nnuxt dev works fine but nuxt build failed\r\n\r\nmessage\r\nERROR Maximum call stack size exceeded\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nNuxi 3.3.1 11:23:50\r\nNuxt 3.3.1 with Nitro 2.3.1 11:23:50\r\ni Using default Tailwind CSS file from runtime/tailwind.css nuxt:tailwindcss 11:23:51\r\ni Building client... 11:23:52\r\ni vite v4.1.4 building for production... 11:23:52\r\ni ✓ 400 modules transformed. 11:23:55 \r\n\r\n ERROR Maximum call stack size exceeded 11:23:55 \r\n\r\n\r\n ERROR Maximum call stack size exceeded 11:23:55 \r\n\r\n at Set.has (\u003Canonymous>)\r\n at ParameterVariable.deoptimizePath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:6801:57)\r\n at Identifier.deoptimizePath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:8149:24)\r\n at ObjectEntity.deoptimizeArgumentsOnInteractionAtPath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:6051:22)\r\n at FunctionExpression.deoptimizeArgumentsOnInteractionAtPath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:8597:36)\r\n at FunctionExpression.deoptimizeArgumentsOnInteractionAtPath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:8973:15)\r\n at ParameterVariable.addEntityToBeDeoptimized (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:6779:20)\r\n at FunctionExpression.deoptimizeArgumentsOnInteractionAtPath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:8589:45)\r\n at FunctionExpression.deoptimizeArgumentsOnInteractionAtPath (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:8973:15)\r\n at ParameterVariable.addEntityToBeDeoptimized (/D:/Algostract/Orykit/store-web/node_modules/rollup/dist/es/shared/node-entry.js:6779:20)\n```\n",[2082,2083,2086,2089,2092],{"name":2058,"color":2059},{"name":2084,"color":2085},"workaround available","11376d",{"name":2087,"color":2088},"bug","d73a4a",{"name":2090,"color":2091},"upstream","E8A36D",{"name":2093,"color":2094},"upstream-bug","B60205",19783,"ERROR Maximum call stack size exceeded","2023-07-02T10:08:00Z","https://github.com/nuxt/nuxt/issues/19783",0.7046588,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"DaBk2NJAxjw3O232fbU4H-q5lif5vGTDDK_sUAEddb8":-1},"/nuxt/test-utils/568"]