\r\n \u003CUInput v-model=\"coverInfoStore.coverTitle\" />\r\n\r\n### Description\r\n\r\nProblem:\r\nWhen using UTextarea component in conjunction with pinia and v-model, there is an inconsistency in behavior compared to using UInput.\r\n\r\nExpected Behavior:\r\nBoth UInput and UTextarea should behave consistently when used with pinia and v-model. Updates to the bound data should reflect immediately in both components.\r\n\r\nActual Behavior:\r\n\r\nWhen updating the data bound to UInput using v-model, the changes are reflected immediately in the UI.\r\nHowever, when updating the data bound to UTextarea using v-model, the changes are not reflected immediately. \r\n\r\n### Additional context\r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3158,3161,3164],{"name":3159,"color":3160},"question","d876e3",{"name":3162,"color":3163},"closed-by-bot","ededed",{"name":3165,"color":3163},"stale",1701,"ui","Inconsistent behavior with UTextarea, pinia, and v-model compared to UInput","2025-06-19T02:12:43Z","https://github.com/nuxt/ui/issues/1701",0.70587546,{"description":3173,"labels":3174,"number":3177,"owner":3140,"repository":3140,"state":3141,"title":3178,"updated_at":3179,"url":3180,"score":3181},"### Environment\n\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.12.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: app, build, css, devtools, modules, runtimeConfig, typescript, vite\r\n- Runtime Modules: @pinia/nuxt@0.4.11\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\npublic npm package: https://github.com/kimbaudi/vue3tslibtest\r\n\r\npublic github repo: https://github.com/kimbaudi/vue3-nuxt-demo\r\n\r\nTo reproduce the error, fork https://github.com/kimbaudi/vue3-nuxt-demo and deploy to vercel.\r\nI already deployed vue3-nuxt-demo to vercel so you can see the error if you go to https://vue3-nuxt-demo.vercel.app/\r\n\r\n\r\n\n\n### Describe the bug\n\nI created a vue3 component library that exports a pinia store and published it as a publicly scoped npm package (https://www.npmjs.com/package/@kimbaudi/vue3tslibtest).\r\n\r\nI then created a nuxt3 project that uses the `@kimbaudi/vue3tslibtest` npm package (https://github.com/kimbaudi/vue3-nuxt-demo).\r\n\r\nWhen I deploy `vue3-nuxt-demo` to vercel, I get a 500 error that module `pinia\\dist\\pinia.prod.cjs` cannot be found imiported from `@kimbaudi\\vue3tslibtest\\dist\\my-lib.js`.\n\n### Additional context\n\nThis issue is related to https://github.com/nuxt/nuxt/issues/19847.\r\n\r\nBefore I deployed `vue3-nuxt-demo` to vercel, I was able to reproduce the issue locally during build (`yarn build`), but not dev (`yarn dev`). After a bit of searching, I discovered issue https://github.com/nuxt/nuxt/issues/19847, which suggested adding the following to `nuxt.config.ts` file in my `vue3-nuxt-demo` project:\r\n\r\n```shell\r\n nitro: {\r\n alias: {\r\n pinia: \"pinia\",\r\n },\r\n },\r\n```\r\n\r\nAfter adding the above configuration, the issue was resolved locally during build so I then proceeded to deploy to vercel. Unfortunately, the 500 cannot find module error exists after deploying to vercel. \r\n\r\nLooking at https://github.com/nuxt/nuxt/issues/19847#issuecomment-1479848806, it seems that `pinia must be installed as a Vue plugin and so it will not work in your server routes, which are run/processed entirely outside of a Vue context`.\r\n\r\n---\r\n\r\nmy npm package `@kimbaudi/vue3tslibtest` has 2 versions: v0.0.1 and v0.0.2.\r\n- v0.0.1 exports pinia store.\r\n- v0.0.2 doesn't export pinia store.\r\n\r\nSo when you fork https://github.com/kimbaudi/vue3-nuxt-demo, you can update @kimbaudi/vue3tslibtest to v0.0.2 in package.json and deploy to vercel and the 500 error will be resolved since I comment out the code that exports the pinia store.\r\n\r\nIf you fork https://github.com/kimbaudi/vue3-nuxt-demo and just keep @kimbaudi/vue3tslibtest at v0.0.1, then you will get the 500 error when deploying to vercel since the pinia store is being exported in that version.\r\n\r\nI'll also open an issue at https://github.com/vuejs/pinia.\n\n### Logs\n\n```shell-script\nError [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/task/node_modules/pinia/dist/pinia.prod.cjs' imported from /var/task/node_modules/@kimbaudi/vue3tslibtest/dist/my-lib.js\r\n at new NodeError (node:internal/errors:399:5)\r\n at finalizeResolution (node:internal/modules/esm/resolve:331:11)\r\n at moduleResolve (node:internal/modules/esm/resolve:994:10)\r\n at moduleResolveWithNodePath (node:internal/modules/esm/resolve:938:12)\r\n at defaultResolve (node:internal/modules/esm/resolve:1202:79)\r\n at nextResolve (node:internal/modules/esm/loader:163:28)\r\n at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)\r\n at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)\r\n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/module_job:77:40)\r\n at link (node:internal/modules/esm/module_job:76:36) {\r\n code: 'ERR_MODULE_NOT_FOUND'\r\n}\r\nError [ERR_MODULE_NOT_FOUND]: Cannot find module '/var/task/node_modules/pinia/dist/pinia.prod.cjs' imported from /var/task/node_modules/@kimbaudi/vue3tslibtest/dist/my-lib.js\r\n at new NodeError (node:internal/errors:399:5)\r\n at finalizeResolution (node:internal/modules/esm/resolve:331:11)\r\n at moduleResolve (node:internal/modules/esm/resolve:994:10)\r\n at moduleResolveWithNodePath (node:internal/modules/esm/resolve:938:12)\r\n at defaultResolve (node:internal/modules/esm/resolve:1202:79)\r\n at nextResolve (node:internal/modules/esm/loader:163:28)\r\n at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)\r\n at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)\r\n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/module_job:77:40)\r\n at link (node:internal/modules/esm/module_job:76:36) {\r\n code: 'ERR_MODULE_NOT_FOUND'\r\n}\n```\n",[3175,3176],{"name":3134,"color":3135},{"name":3137,"color":3138},21854,"Cannot find module `pinia\\dist\\pinia.prod.cjs` when using npm package that exports pinia store only when deployed to vercel","2023-07-03T21:21:58Z","https://github.com/nuxt/nuxt/issues/21854",0.709516,{"description":3183,"labels":3184,"number":3188,"owner":3140,"repository":3140,"state":3141,"title":3189,"updated_at":3190,"url":3191,"score":3192},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: \u003C!-- ex: v2.13.0 -->\"nuxt\": \"^2.14.6\",\r\n- node: \u003C!-- ex: v12.14.0 -->\r\n\r\n### Reproduction\r\nI am creating a custom plugin for axios so it will be injected to root and context ( please don't suggest me to use @nuxt/axios, I am using it as an example ) and in there I am using store as well as i18n.locale. It works fine until I make a change to the vuex state or change locale of i18n, the plugin does not update when any of these these are changed,\r\nSample code: @/plugins/axios.js\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\n```\r\nimport axios from \"axios\";\r\nexport default ({ app, store }, inject) => {\r\n const lang = app.i18n.locale;\r\n const token = store.getters[\"auth/token\"]\r\n const baseAxios = axios.create({\r\n baseURL: \"...\",\r\n headers: {\r\n Authorization: `Bearer ${token}`,\r\n lang\r\n }\r\n });\r\n inject(\"axios\", baseAxios);\r\n};\r\n```\r\n\r\n### What is Expected?\r\nI want the plugin to update to the lates state of vuex. (state of `token` in my case)\r\n\r\n### What is actually happening?\r\nIt is not reactive to store changes",[3185],{"name":3186,"color":3187},"2.x","d4c5f9",8682,"Store in custom plugin is not reactive","2023-01-18T15:31:07Z","https://github.com/nuxt/nuxt/issues/8682",0.7111045,{"description":3194,"labels":3195,"number":3202,"owner":3140,"repository":3167,"state":3141,"title":3203,"updated_at":3204,"url":3205,"score":3206},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAs of now, in Nuxt UI v3.0.0-alpha.x, the `SIDE_OPTIONS` constant is defined as follows:\n\n``` ts\nconst SIDE_OPTIONS: [\"top\", \"right\", \"bottom\", \"left\"];\n```\n\nThe current four directions cannot meet the practical development needs. For example, when there is a button on the far right of the screen to open a dropdown menu, it cannot automatically appear as 'bottom-right'.Tooltips, dropdown menus, or popovers may require positioning beyond the basic cardinal directions to avoid obscuring content or to better fit within the viewport.\n\n#### Proposed Enhancement\n\nI propose to extend the SIDE_OPTIONS constant to include combinations of the cardinal directions to allow for greater flexibility and finer control over positioning. The updated SIDE_OPTIONS would be:\n\n``` ts\nconst SIDE_OPTIONS = [\n \"top\", \"right\", \"bottom\", \"left\",\n \"bottom-left\", \"bottom-right\",\n \"left-top\", \"left-bottom\",\n \"top-left\", \"top-right\",\n \"right-top\", \"right-bottom\"\n];\n```\n\n\n### Additional context\n\n| | |\n| ----------- | ----------- |\n|  | |\n\n\n",[3196,3199],{"name":3197,"color":3198},"enhancement","a2eeef",{"name":3200,"color":3201},"v3","49DCB8",2712,"Side needs more direction","2024-11-20T19:59:29Z","https://github.com/nuxt/ui/issues/2712",0.71207035,{"description":3208,"labels":3209,"number":3212,"owner":3140,"repository":3140,"state":3141,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Environment\r\n\r\nWorking directory: /home/projects/nuxt-starter-yss3ry 11:17:50 pm\r\nNuxt project info: 11:17:50 pm\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.0\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: ssr, modules, vite, devtools\r\n- Runtime Modules: @pinia/nuxt@0.5.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n> Note: I tried downgrading to Nuxt 3.6 and 3.5, still same issue.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-yss3ry?file=pages%2Ffruits.vue\r\n\r\nYou need to run:\r\n```sh\r\nnpm install && npm run generate && pnpm run preview\r\n```\r\n\r\nIn `npm run dev` mode, there is no issue. Only when in static preview mode after payload extraction.\r\n\r\n### Minimal reproduction code [@ stackblitz](https://stackblitz.com/edit/nuxt-starter-yss3ry?file=pages%2Ffruits.vue)\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cmain>\r\n \u003Ch1>fruits.vue page\u003C/h1>\r\n \u003Cp v-if=\"pending\">Loading...\u003C/p>\r\n \u003Cp v-else>fruits: {{ fruits }}\u003C/p>\r\n\r\n \u003Cbr/>\r\n \u003Cbr/>\r\n\r\n \u003Cp>The problem is: \u003Cbr/>\r\n - If you navigate directly to this page, the data is set.\u003Cbr/>\r\n - If you navigate to this page from the home page, the data is NOT set. \r\n \u003Cstrong>That's the bug!\u003C/strong>\r\n \u003C/p>\r\n\r\n \u003Cp>\r\n \u003Cnuxt-link to=\"/\">Home\u003C/nuxt-link>\r\n \u003C/p>\r\n \u003C/main>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nimport { storeToRefs } from \"pinia\";\r\nimport { useExampleStore } from \"~/stores/example\";\r\n\r\nconst exampleStore = useExampleStore();\r\n\r\nconst { getData } = exampleStore;\r\nconst { fruits } = storeToRefs(exampleStore);\r\n\r\nconst { data, pending, error } = useAsyncData(\"get-fruits\", getData);\r\nconsole.log(\">>> THIS IS SET: data.value\", data.value)\r\nconsole.log(\">>> THIS IS **NOT** SET when navigating from /: fruits.value\", fruits.value)\r\n\r\n// debugging payload\r\n// payload still shows the landing page when this is triggered, so the payload was not updated either\r\nonMounted(() => {\r\n const { payload } = useNuxtApp();\r\n //console.log(\"> >>> Payload: \", payload);\r\n console.log(\"> >>> Payload path >>> \", payload.path);\r\n});\r\n \u003C/script>\r\n```\r\n\r\n### Describe the bug\r\n\r\n#### The bug: \r\n- If you start navigation from `/`, then click the nuxt-link to `/fruits`, the pinia store is empty.\r\n- If you start directly at `/fruits` or reload the page, the pinia store is hydrated correctly.\r\n\r\n#### Expected behavior: \r\nFor the payload to hydrate the pinia store in both cases: Navigating directly to `/fruits` page (same as reloading the page), vs starting at root `/` then navigating to `/fruits` page. The should both hydrate the store.\r\n\r\n#### Also noticed: useNuxtApp().payload does not update between page changes. \r\nIt remains stuck at the first page loaded, in this example `/` will be the payload loaded, not `/fruits`.\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nConsole output when you start at `/` then navigate to `/fruits by clicking the link`:\r\n\r\n>>> THIS IS SET: data.value \r\nProxy { \u003Ctarget>: {…}, \u003Chandler>: {…} }\r\n>>> THIS IS **NOT** SET when navigating from /: fruits.value \r\nArray [] \u003C-- the should have 3 fruits!\r\n> >>> Payload path >>> / \u003C-- Notice, the payload.path still `/`\r\n\r\n---\r\n\r\nConsole output when reloading directly `/fruits/`:\r\n\r\n>>> THIS IS SET: data.value \r\nProxy { \u003Ctarget>: {…}, \u003Chandler>: {…} }\r\n>>> THIS IS **NOT** SET when navigating from /: fruits.value \u003C-- 3 fruits, correct\r\nProxy { \u003Ctarget>: (3) […], \u003Chandler>: {…} }\r\n> >>> Payload path >>> /fruits \u003C--- it's correct\r\n```\r\n",[3210,3211],{"name":3134,"color":3135},{"name":3137,"color":3138},23800,"Bug using useAsyncData with ssr: true. Pinia not updated from payload.","2023-11-15T12:56:11Z","https://github.com/nuxt/nuxt/issues/23800",0.7126349,{"description":3218,"labels":3219,"number":3222,"owner":3140,"repository":3140,"state":3141,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.2\r\n- CLI Version: 3.8.3\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: modules, nitro, runtimeConfig\r\n- Runtime Modules: @pinia/nuxt@0.4.11\r\n- Build Modules: \n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-bwuqrs\n\n### Describe the bug\n\nIn my personal project, I have to do two requests on the server side. For this, I was using useAsyncData, making one request, and after it, doing another with the data of the previous request. \r\n\r\nit worked normally when I was using direct axios service. However, when I created a plugin for $api and injected it in the nuxt context, the second request started to throw an error: **A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function**.\r\n\r\nI do these requests inside pinia store, calling useNuxtApp().$api inside of the store, for each request.\r\n\r\nExample of **useAsyncData**:\r\n```\r\nawait useAsyncData('initStore', async () => {\r\n if (process.server) {\r\n const settingsStore = useSettingsStore();\r\n // Change condition to works\r\n if (true) {\r\n await settingsStore.get();\r\n await settingsStore.get();\r\n } else {\r\n console.log('No error');\r\n await Promise.allSettled([settingsStore.get(), settingsStore.get()]);\r\n }\r\n }\r\n});\r\n```\r\n\r\n**Pinia store:** \r\n```\r\nexport const useSettingsStore = defineStore('settingsStore', {\r\n state: () => ({}),\r\n actions: {\r\n async get() {\r\n try {\r\n const { $api } = useNuxtApp();\r\n console.log('$api passed');\r\n } catch (err) { \r\n console.log('error inside catch', err);\r\n } \r\n },\r\n },\r\n});\r\n```\r\n\r\nDo I have to instantiate useNuxtApp inside useAsyncData and pass it to actions inside pinia? Why the second request is throwing this error? Is there a solution for that?\r\n\r\nPs.: If I do both requests at the same time, It works normally, the nuxt context inside pinia works.\r\n\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nError: [nuxt] A composable that requires access to the Nuxt instance was called outside of a plugin, Nuxt hook, Nuxt middleware, or Vue setup function. This is probably not a Nuxt bug. Find out more at `https://nuxt.com/docs/guide/concepts/auto-imports#using-vue-and-nuxt-composables`.\n```\n",[3220,3221],{"name":3134,"color":3135},{"name":3137,"color":3138},23192,"Call useNuxtApp two times in pinia store inside useAsyncData - Nuxt context instance error","2023-09-13T22:49:03Z","https://github.com/nuxt/nuxt/issues/23192",0.71326,{"description":3228,"labels":3229,"number":3232,"owner":3140,"repository":3140,"state":3141,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.1\r\n- Package Manager: npm@9.4.0\r\n- Builder: vite\r\n- User Config: modules, imports\r\n- Runtime Modules: @pinia/nuxt@0.4.11\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-vibihh?file=pages%2Findex.vue,store%2Fwallet.ts\n\n### Describe the bug\n\nI want to modify the value of `isSetOption` to `true` in the `wallet store` by listening to the completion of asynchronous operations in the `chain store`. However, the final result is `false`, and there is no operation in my code to set `isSetOption.value` to `false`.\n\n### Additional context\n\nAlthough the maintainers of Pinia have provided me with a [solution](https://github.com/vuejs/pinia/issues/2285#issuecomment-1612535520) to this issue, I am not sure if it is a bug in Nuxt. So, if this is not a bug, feel free to close the issue.\n\n### Logs\n\n_No response_",[3230,3231],{"name":3134,"color":3135},{"name":3137,"color":3138},21858,"watching asynchronous data can lead to inconsistent values in the store","2023-06-29T08:28:17Z","https://github.com/nuxt/nuxt/issues/21858",0.71331203,{"description":3238,"labels":3239,"number":3245,"owner":3140,"repository":3140,"state":3141,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\r\n\r\nNuxi 3.4.3 Node Version 16.10.0\r\n---- NUXT CONFIG ----\r\n```ts\r\nexport default defineNuxtConfig({\r\n modules: ['@pinia/nuxt', '@nuxt/ui'],\r\n ssr: false,\r\n router: {\r\n middleware: ['layout'],\r\n },\r\n layouts: {\r\n // Specify the default layout for all pages\r\n default: '~/layouts/default.vue',\r\n },\r\n runtimeConfig: {\r\n // The private keys which are only available within server-side\r\n apiSecret: '123',\r\n // Keys within public, will be also exposed to the client-side\r\n public: {\r\n },\r\n },\r\n pinia: {\r\n autoImports: [\r\n // automatically imports `defineStore`\r\n 'defineStore', // import { defineStore } from 'pinia'\r\n ['defineStore', 'definePiniaStore'], // import { defineStore as definePiniaStore } from 'pinia'\r\n ],\r\n },\r\n components: {\r\n path: '~/components',\r\n extensions: ['.vue'],\r\n pathPrefix: false,\r\n global: true,\r\n },\r\n vite: {\r\n css: {\r\n preprocessorOptions: {\r\n scss: {\r\n additionalData: '@import \"@/assets/styles/main.scss\";',\r\n },\r\n },\r\n },\r\n },\r\n publicRuntimeConfig: {\r\n apiURL: process.env.NUXT_API || '',\r\n },\r\n buildModules: [\r\n // Simple usage\r\n '@nuxtjs/dotenv',\r\n ],\r\n plugins: [{ src: './alert.plugin' }]\r\n});\r\n```\r\n---- package.json-----\r\n```json\r\n{\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/ui\": \"^0.3.3\",\r\n \"nuxt\": \"^3.2.3\",\r\n \"postcss\": \"^8.4.21\",\r\n \"prettier\": \"2.8.4\",\r\n \"sass\": \"^1.58.3\",\r\n \"sass-loader\": \"^13.2.0\",\r\n \"tailwindcss\": \"^3.2.7\"\r\n },\r\n \"dependencies\": {\r\n \"@coinbase/wallet-sdk\": \"^3.6.4\",\r\n \"@gnosis.pm/safe-apps-provider\": \"^0.15.1\",\r\n \"@gnosis.pm/safe-apps-sdk\": \"^7.8.0\",\r\n \"@mobiscroll/javascript\": \"^5.22.2\",\r\n \"@nuxt/kit\": \"^3.4.3\",\r\n \"@nuxtjs/dotenv\": \"^1.4.1\",\r\n \"@pinia/nuxt\": \"^0.4.7\",\r\n \"@vueform/multiselect\": \"^2.6.1\",\r\n \"@vuepic/vue-datepicker\": \"^5.0.1\",\r\n \"@vueup/vue-quill\": \"^1.1.1\",\r\n \"@walletconnect/ethereum-provider\": \"^2.7.2\",\r\n \"@walletconnect/web3-provider\": \"^1.8.0\",\r\n \"axios\": \"^1.3.4\",\r\n \"chart.js\": \"^3.9.1\",\r\n \"element-plus\": \"^2.3.4\",\r\n \"ethers\": \"^5.6.9\",\r\n \"flowbite\": \"^1.6.3\",\r\n \"nuxt3\": \"^3.5.0-28064087.90ab1b50\",\r\n \"pinia\": \"^2.0.33\",\r\n \"quill\": \"^1.3.7\",\r\n \"vee-validate\": \"^4.7.4\",\r\n \"vue\": \"^3.3.2\",\r\n \"vue-chart-3\": \"^3.1.8\",\r\n \"vue-dapp\": \"^0.7.2\",\r\n \"vue-demi\": \"^0.13.11\",\r\n \"vue-icomoon\": \"^0.6.1\"\r\n }\r\n}\r\n```\r\n\r\n### Reproduction\r\n\r\nAfter npm i get this error\r\n> npm i \r\n> postinstall\r\n> nuxt prepare\r\n\r\nNuxi 3.4.3 7:13:04 PM\r\n\r\n ERROR Cannot set properties of undefined (setting 'default') 7:13:39 PM\r\n\r\n at build (node_modules/nuxt3/dist/index.mjs:3210:21)\r\n at buildNuxt (node_modules/@nuxt/kit/dist/index.mjs:563:12)\r\n at async Object.invoke (node_modules/nuxi/dist/chunks/prepare.mjs:39:5)\r\n at async _main (node_modules/nuxi/dist/cli.mjs:48:20)\r\n\r\n\r\n### Describe the bug\r\n\r\nAfter the update, I can't start the procester and reinstall node-modules, started getting an error.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\n> postinstall\r\n> nuxt prepare\r\n\r\nNuxi 3.4.3 7:13:04 PM\r\n\r\n ERROR Cannot set properties of undefined (setting 'default') 7:13:39 PM\r\n\r\n at build (node_modules/nuxt3/dist/index.mjs:3210:21)\r\n at buildNuxt (node_modules/@nuxt/kit/dist/index.mjs:563:12)\r\n at async Object.invoke (node_modules/nuxi/dist/chunks/prepare.mjs:39:5)\r\n at async _main (node_modules/nuxi/dist/cli.mjs:48:20)\r\n\r\nnpm ERR! code 1\r\nnpm ERR! path /Users/artem/WebstormProjects/talentum_talents_front_end\r\nnpm ERR! command failed\r\nnpm ERR! command sh -c nuxt prepare\r\n\r\nnpm ERR! A complete log of this run can be found in:\r\nnpm ERR! /Users/artem/.npm/_logs/2023-05-12T17_13_39_562Z-debug.log\r\n```\r\n",[3240,3241,3242],{"name":3134,"color":3135},{"name":3137,"color":3138},{"name":3243,"color":3244},"needs reproduction","FBCA04",20818,"Cannot set properties of undefined (setting 'default') ","2023-05-12T17:55:54Z","https://github.com/nuxt/nuxt/issues/20818",0.7137005,["Reactive",3251],{},["Set"],["ShallowReactive",3254],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8yoGAhmrn8-2Cy33G7A_h_kgbBVkHTMBtlihLuX2ZgA":-1},"/nuxt/ui/3452"]