\r\n \u003CComponentB />\r\n \u003CAsyncComponent />\r\n \u003C/ClientOnly>\r\n\u003C/template>\r\n```\n\n### Additional context\n\nWhen not using `\u003CClientOnly>`, the `defineAsyncComponent` component will be pre-resolved so we can't see the issue at the first loading. (but I think the issue will also exist during page change) \n\n### Logs\n\n_No response_",[3220,3221,3222],{"name":3158,"color":3159},{"name":3161,"color":3162},{"name":3223,"color":3224},"upstream","E8A36D",15648,"loadingComponent property from defineAsyncComponent is ignored","2023-01-19T18:34:58Z","https://github.com/nuxt/nuxt/issues/15648",0.6696372,{"description":3231,"labels":3232,"number":3242,"owner":3170,"repository":3170,"state":3171,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\r\n\r\nNuxt 3.2.2\r\n\r\n### Reproduction\r\n\r\n- Create a project with Nuxt 3.2.2\r\n- Set `ssr: false` in `nuxt.config.ts`\r\n- Create a page\r\n\r\n```\r\n\u003Ctemplate>\r\n\u003C/template>\r\n\u003Cscript lang=\"ts\">\r\nexport default defineNuxtComponent({\r\n async asyncData () {\r\n throw \"error 123\"\r\n }\r\n})\r\n\u003C/script>\r\n```\r\n\r\n### Describe the bug\r\n\r\nIn Nuxt 2 the excepton occurs in asyncData will be catch and pass to the error page, we can handle the error properly.\r\n\r\nIn Nuxt 3 it simply gone, we can't even see the error in console 🤣🤣🤣\r\nThe only output in console is `[nuxt] asyncData should return an object` and we know we get fucked something wrong in the asyncData function.\r\n\r\nIs option api and asyncData no longer supported?\r\nCan you guys save programers migrating from Nuxt 2? We are in the hell.\r\n\r\nFor people has same issue, here is a workround for this ridiculous bug:\r\n\r\n- Add isReady to data()\r\n- Add `v-if=\"isReady\"` to the root element\r\n- Move all logic from asyncData to created\r\n- Add `this.isReady = true` at the end of created\r\n- Exceptions from created will be well handled not like asyncData, I think this function may no longer supported\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3233,3236,3237,3240],{"name":3234,"color":3235},"good first issue","fbca04",{"name":3158,"color":3159},{"name":3238,"color":3239},"dx","C39D69",{"name":3241,"color":3168},"🔨 p3-minor",19625,"Any exception from asyncData will be discard in Nuxt 3","2023-04-27T10:51:35Z","https://github.com/nuxt/nuxt/issues/19625",0.68187267,{"description":3248,"labels":3249,"number":3252,"owner":3170,"repository":3170,"state":3171,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\n\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.17.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.18`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nCreate new project and add a new plugin (/plugins/init.server.js) with the following code : \r\n\r\n```\r\nexport default defineNuxtPlugin(async () => {\r\n await test();\r\n})\r\n\r\nconst test = async () => {\r\n let promise = new Promise((resolve, reject) => {\r\n setTimeout(() => resolve(\"done!\"), 1000)\r\n });\r\n const nuxtApp1 = useNuxtApp();\r\n await promise;\r\n const nuxtApp2 = useNuxtApp();\r\n return Promise.resolve();\r\n};\r\n```\n\n### Describe the bug\n\nAn error is triggered on the second call of the useNuxtApp, because it is after an await call.\r\n\r\n```\r\n[nuxt] [request error] [unhandled] [500] nuxt instance unavailable \r\n at Module.useNuxtApp (./node_modules/nuxt/dist/app/nuxt.mjs:165:13) \r\n at test (./plugins/init.server.js:16:42) \r\n at async ./plugins/init.server.js:7:73 \r\n at async Object.callAsync (./node_modules/unctx/dist/index.mjs:53:16) \r\n at async applyPlugin (./node_modules/nuxt/dist/app/nuxt.mjs:97:23) \r\n at async Module.applyPlugins (./node_modules/nuxt/dist/app/nuxt.mjs:107:5) \r\n at async createNuxtAppServer (./node_modules/nuxt/dist/app/entry.mjs:29:7) \r\n at async default (./node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:27:18) \r\n at async Object.renderToString (./node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19) \r\n at async ./.nuxt/dev/index.mjs:630:21\r\n```\n\n### Additional context\n\nI encountered this bug while migrating my website from Nuxt 2 to Nuxt 3.\r\nThe same bug happen in a asyncData method of a page component, like this : \r\n\r\napp.vue : \r\n```\r\n\u003Cscript>\r\nimport { test } from \"@/utils/test\"\r\n\r\nexport default defineNuxtComponent({\r\n async asyncData() {\r\n await test();\r\n return {};\r\n }\r\n});\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtWelcome />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nutils/test.js :\r\n```\r\nexport const test = async () => {\r\n let promise = new Promise((resolve, reject) => {\r\n setTimeout(() => resolve(\"done!\"), 1000)\r\n });\r\n const nuxtApp1 = useNuxtApp();\r\n await promise;\r\n const nuxtApp2 = useNuxtApp();\r\n return Promise.resolve();\r\n}\r\n``` \r\n\n\n### Logs\n\n_No response_",[3250,3251],{"name":3158,"color":3159},{"name":3161,"color":3162},15786,"[Nuxt 3] Nuxt instance unavailable in async actions during SSR","2023-01-19T18:20:59Z","https://github.com/nuxt/nuxt/issues/15786",0.68409693,{"description":3258,"labels":3259,"number":3265,"owner":3170,"repository":3170,"state":3171,"title":3266,"updated_at":3267,"url":3268,"score":3269},"### Environment\n\nOperating System: Windows 10\nNode Version: v22.11.0\nNuxt Version: v3.16.0\nCLI Version: v3.22.5\nNitro Version: v2.11.6\nPackage Manager: pnpm@10.2.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-tvzgp4e7?file=plugins%2Ftest.ts\n\n### Describe the bug\n\nI defined a plugin in the `plugins` directory and used components from `@element-plus/nuxt` in the plugin. After upgrading to Nuxt v3.16.0, the development environment runs without any issues, and there are no errors when running `pnpm build`. However, when I start the preview with `pnpm preview`, the page returns a 500 error and becomes inaccessible. The console shows the following error message:\n```\n[request error] [unhandled] [GET] http://localhost:3000/home\n ReferenceError: shared_cjs_prodExports is not defined\n at file:///E:/Project_private/test/.output/server/chunks/build/server.mjs:35957:1\n ... 6 lines matching cause stack trace ...\n at async Server.toNodeHandle (file:///E:/Project_private/test/.output/server/chunks/_/nitro.mjs:1878:7) {\n cause: ReferenceError: shared_cjs_prodExports is not defined\n at file:///E:/Project_private/test/.output/server/chunks/build/server.mjs:35957:1\n at ModuleJob.run (node:internal/modules/esm/module_job:268:25)\n at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:543:26)\n at async file:///E:/Project_private/test/.output/server/chunks/routes/renderer.mjs:117:24\n at async Object.render (file:///E:/Project_private/test/.output/server/chunks/routes/renderer.mjs:272:64)\n at async Object.handler (file:///E:/Project_private/test/.output/server/chunks/_/nitro.mjs:4760:22)\n at async Object.handler (file:///E:/Project_private/test/.output/server/chunks/_/nitro.mjs:1607:19)\n at async Server.toNodeHandle (file:///E:/Project_private/test/.output/server/chunks/_/nitro.mjs:1878:7),\n statusCode: 500,\n fatal: false,\n unhandled: true,\n statusMessage: undefined,\n data: undefined\n}\n```\n\nI found that in the output directory `.output/server/chunks/build/server.mjs`, the method `requireShared_cjs_prod` is called to generate `shared_cjs_prodExports$1`, but there is a `shared_cjs_prodExports.hasOwn` code appearing below it. This issue only occurs when using the `pnpm` package manager. Everything works fine when I roll back to Nuxt v3.15.4.\n\n### Additional context\n\nEverything works fine when I use the `npm` package manager. This issue only occurs when using the `pnpm` package manager.\n\n### Logs\n\n```shell-script\n\n```",[3260,3261,3262],{"name":3200,"color":3201},{"name":3161,"color":3162},{"name":3263,"color":3264},"possible regression","B90A42",31352,"Nuxt 3.16.0 build and run preview error 500 ReferenceError: shared_cjs_prodExports is not defined","2025-04-18T11:02:35Z","https://github.com/nuxt/nuxt/issues/31352",0.6842332,{"description":3271,"labels":3272,"number":3277,"owner":3170,"repository":3170,"state":3171,"title":3278,"updated_at":3279,"url":3280,"score":3281},"### Environment\n\nOperating System: MacOS\nNode Version: v22.17.1\nNuxt Version: 4.0.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-dsvrg6zf\n\n### Describe the bug\n\nWhen upgrading from nuxt 4.0.1 to 4.0.3 I noticed that a new error started appearing on the application start, after trying to change all the nuxt config I noticed the problem came from this vite configuration that we were using because of an issue while upgrading a previous version of nuxt as can be seen here: https://github.com/nuxt/nuxt/issues/32581\n\n```\n vite: {\n // Once vite/nitro/rollup fixes https://github.com/nuxt/nuxt/issues/32581 we can remove the ssr: noExternal\n ssr: {\n noExternal: true,\n },\n },\n```\n\nMaybe we don't need that configuration anymore but I guess anyone that uses it will face the same issue upgrading, should this be reflect in the docs ? Should it be a warning ? \n\nThe issue on the UI\n\u003Cimg width=\"599\" height=\"961\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d8078bda-da0a-41fb-b90b-5cd3b8b08065\" />\n\n### Additional context\n\nRelated issues: https://github.com/nuxt/nuxt/issues/32812 this one was closed as there was no reproduction\n\n\n\n### Logs\n\n```shell-script\n\n```",[3273,3276],{"name":3274,"color":3275},"🍰 p2-nice-to-have","0E8A16",{"name":3263,"color":3264},32948,"\"#app/entry\" is not defined in package when using nuxt 4.0.2 onwards","2025-09-04T10:41:55Z","https://github.com/nuxt/nuxt/issues/32948",0.6844688,["Reactive",3283],{},["Set"],["ShallowReactive",3286],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fygDIN8aGWNk9IAlhghNzOLI3QxAB7UsQ-2xsxYusmqM":-1},"/nuxt/nuxt/13773"]