\r\n \u003Cbutton class=\"input-number-add\">\r\n \u003Cspan class=\"visually-hidden\">Aumenta valore Euro\u003C/span>\r\n \u003C/button>\r\n \u003Cbutton class=\"input-number-sub\">\r\n \u003Cspan class=\"visually-hidden\">Diminuisci valore Euro\u003C/span>\r\n \u003C/button>\r\n \u003C/span>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nimport { InputNumber } from 'bootstrap-italia'\r\n\r\nexport default {\r\n name: 'NuxtTutorial',\r\n onMounted: () => {\r\n new InputNumber(document.getElementById('inputNumber3'))\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\nNo particular configuration.\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\n\r\n- Install a tree shakable library (in this case bootstrap-italia). See the code above and look the final js, it includes all the components exported in index.js by bootstrap-italia\r\n\r\n### What is Expected?\r\n\r\nI'd like to see the same behaviour both during development and production\r\n\r\n### What is actually happening?\r\n\r\nIn production tree shake works as expected, during development I see all my components imported!\r\n",[3214,3217],{"name":3215,"color":3216},"pending triage","E99695",{"name":3218,"color":3219},"2.x","d4c5f9",10795,"Treeshaking not working in dev mode","2023-01-22T15:48:35Z","https://github.com/nuxt/nuxt/issues/10795",0.69138014,{"description":3226,"labels":3227,"number":3231,"owner":3184,"repository":3184,"state":3206,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Environment\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.2.0`\r\n- Nitro Version: `2.2.1`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-732ozv?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nWhen you wrap async component in client-only nuxt throws error\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3228,3229,3230],{"name":3194,"color":3195},{"name":3197,"color":3198},{"name":3200,"color":3201},18949,"ClientOnly treeshake error with async components","2023-02-16T12:47:44Z","https://github.com/nuxt/nuxt/issues/18949",0.6924804,{"description":3237,"labels":3238,"number":3242,"owner":3184,"repository":3184,"state":3206,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### Environment\n\n```shell\r\nNuxt project info: 13:07:25\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.0\r\n- Nitro Version: 2.6.1\r\n- Package Manager: pnpm@8.6.12\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nOpen the following SB repo using `virtual:pwa-info`: \r\nhttps://stackblitz.com/edit/nuxt-starter-dnvrut?file=app.vue,package.json,nuxt.config.ts\r\n\r\nOnce Nuxt starts, there is a warning about resolving `virtual:pwa-info` (should be `\\0virtual:pwa-info`):\r\n\r\n\r\nYou can also reproduce it in the nuxt repo using the playground , just add this to the playground `nuxt.config.ts` file:\r\n```ts\r\nconst virtual = 'virtual:xxx'\r\nconst resolvedVirtual = `\\0${virtual}`\r\n\r\nexport default defineNuxtConfig({\r\n vite: {\r\n plugins: [{\r\n name: 'xxx',\r\n enforce: 'post',\r\n resolveId (id) {\r\n if (id === virtual) {\r\n console.log('xxx:resolveId', id, resolvedVirtual)\r\n return resolvedVirtual\r\n }\r\n },\r\n load (id) {\r\n if (id === resolvedVirtual) {\r\n console.log('xxx:load', id, resolvedVirtual)\r\n return 'export const xxx = \"xxx\";'\r\n }\r\n }\r\n }]\r\n }\r\n})\r\n```\r\n\r\nAdd this component on playground folder:\r\n```ts\r\nimport { defineComponent } from 'vue'\r\nimport { xxx } from 'virtual:xxx'\r\n\r\nexport default defineComponent({\r\n setup () {\r\n if (xxx) {\r\n console.log(xxx)\r\n }\r\n\r\n return () => null\r\n }\r\n})\r\n```\r\n\r\nAnd add the component to the `app.vue`:\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport VirtualComponent from './VirtualComponent'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CVirtualComponent />\r\n \u003C!-- Edit this file to play around with Nuxt but never commit changes! -->\r\n \u003Cdiv>\r\n Nuxt 3 Playground\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle scoped>\r\n\r\n\u003C/style>\r\n```\r\n\r\nYou will see the warning once Nuxt starts:\r\n```shell\r\n[nuxt] Could not resolve id virtual:xxx D:\\work\\projects\\userquin\\GitHub\\userquin\\nuxt-org\\nuxt\\playground\\index.html\r\n```\n\n### Describe the bug\n\nResolved Vite virtual modules should be also excluded, `\\0virtual:` should also be excluded: https://vitejs.dev/guide/api-plugin.html#virtual-modules-convention.\r\n\r\nThere are a few modules only checking for `virtual:` prefix, we should also review the usage:\r\n\r\n\r\n\r\n\r\nI'm preparing a PR.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3239,3240,3241],{"name":3194,"color":3195},{"name":3197,"color":3198},{"name":3200,"color":3201},22833,"exclude also default resolved Vite virtual modules","2023-08-26T14:45:18Z","https://github.com/nuxt/nuxt/issues/22833",0.70907056,{"description":3248,"labels":3249,"number":3252,"owner":3184,"repository":3253,"state":3206,"title":3254,"updated_at":3255,"url":3256,"score":3257},"",[3250],{"name":3197,"color":3251},"ff281a",1239,"nuxt.com","Add missing clipboard feature","2023-02-20T09:39:27Z","https://github.com/nuxt/nuxt.com/issues/1239",0.71025664,{"description":3259,"labels":3260,"number":3273,"owner":3184,"repository":3274,"state":3206,"title":3275,"updated_at":3276,"url":3277,"score":3278},"### Environment\n\n- Ubuntu (WSL 2)\n- Package manager Bun\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n[Reproduction repository](https://github.com/sergiooak/vue-nuxtui-bun-type-import)\n\n\n### Description\n\nI found a weird bug while import types from @nuxt/ui using the syntax \"import { type ComponentProps} from @nuxt/ui\"\nIt took me a long time to pinpoint what was causing the bug. If i use this syntax, and do a fresh install, in my case, bun i && bun dev, I got this weird \"internal\" error from tailwind without point exactly where the error is.\n\nIf I clean the node_modules rewrite the import to \"import type {ComponentProps} from @nuxt/ui\" bun i && bun dev, the problem solves.\n\nI don't know if this is bun related or not, I am creating a minimal reproduction repo using npm and bun ASAP\n(I've just already created the issue in case someone find this bug in the meantime)\n\n### Additional context\n\nThe bug occurs only when using bun install with this specific import syntax for @nuxt/ui. Other imports using the same syntax work as expected. If bun install is run without this syntax, and the code is then adjusted accordingly, everything works fine. I only noticed this issue a few commits later due to this behavior\n\n### Logs\n\n```shell-script\n✘ [ERROR] Could not resolve \"../pkg\"\n\n node_modules/lightningcss/node/index.js:16:27:\n 16 │ module.exports = require(`../pkg`);\n ╵ ~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38:\n 190 │ ...inding = require('@tailwindcss/oxide-linux-x64-gnu')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38:\n 177 │ ...nding = require('@tailwindcss/oxide-linux-x64-musl')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476\n let error = new Error(text);\n ^\n\nError: Build failed with 3 errors:\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\nnode_modules/lightningcss/node/index.js:16:27: ERROR: Could not resolve \"../pkg\"\n at failureErrorWithLog (/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476:15)\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:945:25\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1354:9\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {\n errors: [Getter/Setter],\n warnings: [Getter/Setter]\n}\n```",[3261,3262,3265,3268,3271],{"name":3197,"color":3198},{"name":3263,"color":3264},"v3","49DCB8",{"name":3266,"color":3267},"triage","ffffff",{"name":3269,"color":3270},"closed-by-bot","ededed",{"name":3272,"color":3270},"stale",3039,"ui","Unexpected Bug with Tree-Shaking Type Imports in @nuxt/ui","2025-06-18T09:02:41Z","https://github.com/nuxt/ui/issues/3039",0.7154172,{"description":3280,"labels":3281,"number":3284,"owner":3184,"repository":3184,"state":3206,"title":3285,"updated_at":3286,"url":3287,"score":3288},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.9.0`\r\n- Nuxt Version: `3.13.0`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\n* Create a new project like `npx nuxi init bundle-size-test`\r\n* Run `nuxi analyze` inside the project\r\n* Open the client bundle stats\n\n### Describe the bug\n\nThe Vue packages are 32kb gzipped. \r\n\r\n\r\n\r\nAccording to the [Vue docs](https://vuejs.org/about/faq#is-vue-lightweight), the maximum size of Vue should be around 27kb (brotli), but can be as low as 16kb depending on how many features are used. Since this is a minimal app, I would expect it to be on the lower side. Is it possible that tree-shaking is not working correctly?\r\n\n\n### Additional context\n\nFollow up from the discussion here: https://github.com/nuxt/nuxt/discussions/23729\n\n### Logs\n\n_No response_",[3282,3283],{"name":3215,"color":3216},{"name":3203,"color":3204},28808,"Possible issue with tree-shaking Vue during build","2024-09-05T11:33:23Z","https://github.com/nuxt/nuxt/issues/28808",0.7164773,{"description":3290,"labels":3291,"number":3296,"owner":3184,"repository":3184,"state":3206,"title":3297,"updated_at":3298,"url":3299,"score":3300},"### Environment\r\n\r\nnpx nuxi info\r\nNuxi 3.6.5 \r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: app, ssr, spaLoadingTemplate, extends, watch, modules, imports, devServer, nitro, vite, router, components, hooks \r\n- Runtime Modules: @pinia/nuxt@0.4.11, @nuxtjs/tailwindcss@6.8.0, @vueuse/nuxt@10.3.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nI don't have any idea why this is happening. I have one root project and child projects with layering. And this happens when `nuxi generate` one of child projects. Does anyone have any ideas?\r\n\r\n`nuxt.config.ts` below:\r\n```\r\n{\r\n ssr: false,\r\n spaLoadingTemplate: false,\r\n extends: ['../core'],\r\n watch: [process.env.NODE_ENV === 'development' ? '../core' : ''],\r\n\r\n modules: ['@pinia/nuxt', '@nuxtjs/tailwindcss', '@vueuse/nuxt'],\r\n\r\n imports: {\r\n dirs: ['store'],\r\n },\r\n\r\n devServer: {\r\n port: 8080,\r\n },\r\n\r\n nitro: {\r\n compressPublicAssets: true,\r\n output: {\r\n publicDir: import.meta.env.VITE_BUILD_DIR,\r\n },\r\n },\r\n\r\n vite: {\r\n build: {\r\n minify: false,\r\n rollupOptions: {\r\n output: {\r\n entryFileNames: `_nuxt/[name].js`,\r\n chunkFileNames: `_nuxt/[name].js`,\r\n assetFileNames: `_nuxt/[name].[ext]`,\r\n },\r\n },\r\n },\r\n },\r\n ```\r\n \r\n `package.json`:\r\n ```\r\n {\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev --dotenv .env.development\",\r\n \"test\": \"nuxt dev --dotenv .env.test\",\r\n \"prod\": \"nuxt dev --dotenv .env.production\",\r\n \"vercel\": \"nuxt dev --dotenv .env.vercel\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\",\r\n \"typecheck\": \"nuxt typecheck\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/devtools\": \"^0.4.5\",\r\n \"@vueuse/nuxt\": \"^10.3.0\",\r\n \"nuxt\": \"^3.6.5\",\r\n \"prettier\": \"^2.8.8\"\r\n },\r\n \"dependencies\": {\r\n \"@nuxtjs/tailwindcss\": \"^6.8.0\",\r\n \"@pinia/nuxt\": \"^0.4.11\",\r\n \"pinia\": \"^2.1.6\"\r\n }\r\n}\r\n```\r\n\r\n### Describe the bug\r\n\r\nI get such error\r\n```\r\n[4/4] Building fresh packages...\r\n$ nuxt prepare\r\n[log] Nuxi 3.6.5\r\n[error] Cannot find module '...\\efo\\efo\\node_modules\\nuxt\\node_modules\\@nuxt\\kit\\dist\\index.mjs' imported from '...\\efo\\efo\\node_modules\\nuxt\\dist\\index.mjs'\r\n at new NodeError (node:internal/errors:399:5)\r\n at finalizeResolution (node:internal/modules/esm/resolve:326:11)\r\n at moduleResolve (node:internal/modules/esm/resolve:945:10)\r\n at defaultResolve (node:internal/modules/esm/resolve:1153:11)\r\n at nextResolve (node:internal/modules/esm/loader:1[63](https://gitlab.halyklife.nb/dit/front-vue/efo/-/jobs/11694#L63):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\nerror Command failed with exit code 1.\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_",[3292,3293,3294],{"name":3194,"color":3195},{"name":3215,"color":3216},{"name":3295,"color":3201},"needs reproduction",22460,"Cannot find module `...\\nuxt\\node_modules\\@nuxt\\kit\\dist\\index.mjs`","2023-10-20T11:00:44Z","https://github.com/nuxt/nuxt/issues/22460",0.71789306,{"description":3302,"labels":3303,"number":3305,"owner":3184,"repository":3184,"state":3206,"title":3306,"updated_at":3307,"url":3308,"score":3309},"### Environment\n```\n❯ npx nuxi info\nWorking directory: /home/projects/sb1-vh6z4urm/packages/my-module nuxi 3:49:00 PM\nNuxt project info: nuxi 3:49:00 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.15.4\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/sb1-vh6z4urm?file=packages%2Fmy-module%2Fsrc%2Fruntime%2Fserver%2Fapi%2Fchallenge.get.ts\n\n### Describe the bug\n\nI am developing a package in a pnpm monorepo. Inside the `packages` folder you can find the a Nuxt module.\n\nWithing that module I use `await installModule('nuxt-auth-utils')` which is another Nuxt Module for auth.\n\nThis module specifically exports some vue composables (`useUserEvent`) and some [server utils](https://github.com/atinux/nuxt-auth-utils?tab=readme-ov-file#server-utils) like `clearUserSession, getUserSession, setUserSession` which I would like to use in my server and composables as well.\n\nIf I run `pnpm install && pnpm dev:prepare` within the `my-module` folder, the types are getting generated as expected and everything seems to work.\n\nNow, if I do `pnpm install && pnpm run --filter packages/my-module dev:prepare` then the `.nuxt` folder produced by Nuxt is different and the utilities from `nuxt-auth-utils` are no longer available.\n\n\n### Additional context\n\n## What I have tried\n\n1. Tried to define `.npmrc`\n\n```\npublic-hoist-pattern[]=*types*\npublic-hoist-pattern[]=@nuxt/*\npublic-hoist-pattern[]=nuxt-auth-utils\nshamefully-hoist=true\n```\n\n2. Installing `nuxt-auth-utils` in the root.\n\n\nDoes anyone know why I might be doing wrong?\nAny work around?\n\n\nThank you!\n\n### Logs\n\n```shell-script\n\n```",[3304],{"name":3215,"color":3216},30816,"[Nuxt modules] Unable to use exported methods from other modules in my module","2025-02-21T13:35:55Z","https://github.com/nuxt/nuxt/issues/30816",0.71840227,["Reactive",3311],{},["Set"],["ShallowReactive",3314],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzO9Ue9dk9EURHUz2ab-U96SO-ConmXWR7AbJDWT3lfw":-1},"/nuxt/ui/3376"]