\n\n\u003Cimg width=\"372\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/767441c1-d191-4c21-bf1e-56576b942a02\" />\n\nHTML output\n\u003Cimg width=\"292\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6a2bc536-20a5-40ae-b882-91cf581e2e8f\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3250,3251],{"name":3172,"color":3173},{"name":3212,"color":3213},30761,"The shared folder doesn't work as documented in layers setup","2025-02-12T10:26:23Z","https://github.com/nuxt/nuxt/issues/30761",0.6935407,{"description":3258,"labels":3259,"number":3262,"owner":3175,"repository":3175,"state":3215,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v19.3.0`\r\n- Nuxt Version: `3.8.0`\r\n- CLI Version: `3.9.1`\r\n- Nitro Version: `2.7.2`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `-`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/halilyuce/monorepo\r\n\r\n### Describe the bug\r\n\r\nHere is my monorepo structure:\r\n\r\n\u003Cimg width=\"297\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/29376592/7a1f6640-6b7b-4f63-aa0e-62adce755b01\">\r\n\r\nI created a monorepo with npm workspaces and extended apps in the portal(main app) thanks to nuxt layers. Everything works as expected in production mode but not in dev mode?\r\n\r\nWhen I run the project in dev mode, I do not receive any errors. It stays on the nuxt loading screen and the computer starts to heat up seriously and the fans become loud, probably a memory problem. \r\n\r\nI have a decent laptop, according to my research, this problem occurs because the node_modules location changes when using monorepo. I applied dozens of solutions for this, but none of them worked.\r\n\r\n\u003Cimg width=\"454\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/29376592/cd338d5c-9071-43a9-9006-3e25e82f2169\">\r\n\r\n\r\n\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_No response_",[3260,3261],{"name":3203,"color":3204},{"name":3172,"color":3173},24049,"Nuxt Layers + Npm Workspaces(Monorepo) Doesn't work only in Dev Mode","2023-10-31T21:23:22Z","https://github.com/nuxt/nuxt/issues/24049",0.69792306,{"description":3268,"labels":3269,"number":3272,"owner":3175,"repository":3175,"state":3215,"title":3273,"updated_at":3274,"url":3275,"score":3276},"### Environment\n\nWindows 11 > WSL2 Ubuntu\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.11.0`\r\n- Nuxt Version: `2.15.8`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `pnpm@7.14.2`\r\n- Builder: `webpack`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nMinimal reproduction here: https://github.com/Suniron/monorepo-nuxt2-nuxt3-problem\r\n\r\nTry to install with `pnpm install` in root folder\n\n### Describe the bug\n\nHey,\r\n\r\nI'm working on a monorepo (with turborepo) of a big project using Nuxt 2 as web interface.\r\n\r\nI need to create a second web app which using Nuxt 3 but i can't start this app in the monorepo, i got this error when i try to install the project (`pnpm i` at root):\r\n\r\n```\r\nScope: all 7 workspace projects\r\nLockfile is up to date, resolution step is skipped\r\nAlready up to date\r\napps/nuxt3-app postinstall$ nuxt prepare\r\n│ Nuxi 3.0.0\r\n│ ℹ Client built in 7475ms\r\n│ ℹ Building server...\r\n│ ERROR [commonjs--resolver] Missing \"./server-renderer\" export in \"vue\" package\r\n│ ERROR Missing \"./server-renderer\" export in \"vue\" package\r\n```\r\n\r\nI think the problem is because the root node_modules is shared.\r\n\r\nI just pushed a simple version of my project here which reproduce the problem:\r\n\r\nhttps://github.com/Suniron/monorepo-nuxt2-nuxt3-problem\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3270,3271],{"name":3203,"color":3204},{"name":3172,"color":3173},12331,"Impossible to have Nuxt 2 and Nuxt 3 in same monorepo: Nuxt 3 can't do postinstall","2023-11-30T12:59:06Z","https://github.com/nuxt/nuxt/issues/12331",0.6999803,{"description":3278,"labels":3279,"number":3282,"owner":3175,"repository":3175,"state":3215,"title":3283,"updated_at":3284,"url":3285,"score":3286},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v14.20.1`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `pnpm@7.14.1`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nℹ️ All works fine with `nuxt@3.0.0-rc.11`, error occur only with `nuxt@3.0.0-rc.12`.\r\n\r\n1. Create a new monorepo project.\r\n2. Add a single name in the `package.json` file of each Nuxt projects.\r\n3. Add `pnpm-workspace.yaml` to the root folder.\r\n4. Follow all `pnpm` steps on the [Nuxt installation](https://v3.nuxtjs.org/getting-started/installation/) page, for each projects.\r\n5. Run `pnpm --filter my-project-name dev -o` to the root folder.\r\n6. Error 500: `Unexpected token '||='`.\n\n### Describe the bug\n\nAfter \"Nitro built\" terminal message, there is an error 500 with the message: `Unexpected token '||='`.\r\n\r\n```\r\n500\r\nUnexpected token '||='\r\n\r\nat new Script (vm.js:102:7)\r\nat createScript (vm.js:262:10)\r\nat Object.runInThisContext (vm.js:310:10)\r\nat ViteNodeRunner.directRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:245:19)\r\nat processTicksAndRejections (internal/process/task_queues.js:95:5)\r\nat async ViteNodeRunner.cachedRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:129:12)\r\nat async request (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:152:16)\r\nat async /Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/nuxt@3.0.0-rc.12/node_modules/nuxt/dist/app/composables/index.mjs:46:31\r\nat async ViteNodeRunner.directRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:250:5)\r\nat async ViteNodeRunner.cachedRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:129:12)\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell\nat new Script (vm.js:102:7)\r\nat createScript (vm.js:262:10)\r\nat Object.runInThisContext (vm.js:310:10)\r\nat ViteNodeRunner.directRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:245:19)\r\nat processTicksAndRejections (internal/process/task_queues.js:95:5)\r\nat async ViteNodeRunner.cachedRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:129:12)\r\nat async request (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:152:16)\r\nat async /Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/nuxt@3.0.0-rc.12/node_modules/nuxt/dist/app/composables/index.mjs:46:31\r\nat async ViteNodeRunner.directRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:250:5)\r\nat async ViteNodeRunner.cachedRequest (/Users/bgd/Documents/Projects/scores-plus/node_modules/.pnpm/vite-node@0.24.5/node_modules/vite-node/dist/client.mjs:129:12)\n```\n",[3280,3281],{"name":3203,"color":3204},{"name":3172,"color":3173},15325,"Pnpm workspace - Error 500: Unexpected token '||='","2023-01-19T17:48:17Z","https://github.com/nuxt/nuxt/issues/15325",0.70024544,["Reactive",3288],{},["Set"],["ShallowReactive",3291],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fY5xHDUcJf92A7WqYn-9roDIfyTMWAa1EK7cP7ZplyVA":-1},"/nuxt/nuxt/26065"]