\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",[3139,3142],{"name":3140,"color":3141},"pending triage","E99695",{"name":3143,"color":3144},"2.x","d4c5f9",10795,"nuxt","closed","Treeshaking not working in dev mode","2023-01-22T15:48:35Z","https://github.com/nuxt/nuxt/issues/10795",0.71636057,{"description":3153,"labels":3154,"number":3167,"owner":3146,"repository":3146,"state":3147,"title":3168,"updated_at":3169,"url":3170,"score":3171},"> I noticed that the `'builder:watch'` hook won't be release after the nuxt.config is updated. As the dev server is restarted, this hook will be registered multiple times.\r\n>\r\n> I don't know if this behavior is expected, but it never happened when I was developing modules three months ago. There may be some similarities between these issues.\r\n\r\n_Originally posted by @Teages in https://github.com/nuxt/nuxt/issues/27515#issuecomment-2162035225_\r\n",[3155,3158,3161,3164],{"name":3156,"color":3157},"3.x","29bc7f",{"name":3159,"color":3160},"bug","d73a4a",{"name":3162,"color":3163},"🔨 p3-minor","FBCA04",{"name":3165,"color":3166},"performance","E84B77",27570,"'builder:watch' hook isn't released when nuxt.config is updated","2024-06-12T19:55:26Z","https://github.com/nuxt/nuxt/issues/27570",0.7250221,{"description":3173,"labels":3174,"number":3182,"owner":3146,"repository":3146,"state":3147,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Environment\n\nnpm run build\n\n### Reproduction\n\n\r\nThe company code is not available\r\n\r\nCan you guys look at the description for possible reasons?\n\n### Describe the bug\n\n\u003Cimg width=\"1268\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/22836707/82257992-d98d-4878-ae2b-e3df8802aea4\">\r\n\u003Cimg width=\"869\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/22836707/2fc6095d-7ff8-48d9-b001-6e854e29835a\">\r\n\r\nsvg-icon/index-old.vue unused but chunks have it\r\n\r\nsvg-icon/index.vue used\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3175,3176,3177,3179],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3178,"color":3163},"needs reproduction",{"name":3180,"color":3181},"closed-by-bot","ededed",22587,"Why am I not using this component, nuxt will build the product this component to chunks","2023-08-19T01:45:39Z","https://github.com/nuxt/nuxt/issues/22587",0.7255911,{"description":3188,"labels":3189,"number":3192,"owner":3146,"repository":3193,"state":3147,"title":3194,"updated_at":3195,"url":3196,"score":3197},"",[3190],{"name":3159,"color":3191},"ff281a",1239,"nuxt.com","Add missing clipboard feature","2023-02-20T09:39:27Z","https://github.com/nuxt/nuxt.com/issues/1239",0.72749245,{"description":3199,"labels":3200,"number":3203,"owner":3146,"repository":3146,"state":3147,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### Describe the feature\n\nI find options to disable `minify` in `nuxt2`\r\nbut not find in `nuxt3`. https://nuxt.com/docs/guide/directory-structure/nuxt.config\r\nhow to disable `minify` in `nuxt3` ?\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3201,3202],{"name":3156,"color":3157},{"name":3140,"color":3141},23315,"how to disable `minify` in `nuxt generate`","2023-09-21T07:54:26Z","https://github.com/nuxt/nuxt/issues/23315",0.7293184,{"description":3209,"labels":3210,"number":3214,"owner":3146,"repository":3146,"state":3147,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### 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_",[3211,3212,3213],{"name":3156,"color":3157},{"name":3159,"color":3160},{"name":3162,"color":3163},18949,"ClientOnly treeshake error with async components","2023-02-16T12:47:44Z","https://github.com/nuxt/nuxt/issues/18949",0.7316675,{"labels":3220,"number":3223,"owner":3146,"repository":3146,"state":3147,"title":3224,"updated_at":3225,"url":3226,"score":3227},[3221,3222],{"name":3156,"color":3157},{"name":3140,"color":3141},14250,"Composables that use useNuxtApp internally don't work after async functions!","2023-01-19T17:31:10Z","https://github.com/nuxt/nuxt/issues/14250",0.7320902,{"description":3229,"labels":3230,"number":3236,"owner":3146,"repository":3146,"state":3147,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.10.0\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@8.19.2\r\n- Builder: -\r\n- User Config: modules, site, sitemap, robots, ogImage, linkChecker, head, routeRules, extends, typescript, sourcemap, devServer, htmlValidator, image, runtimeConfig, schemaOrg, nitro, appConfig, ignore, hooks, css, vite\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @nuxt/content@2.7.2, @nuxt/image-edge@1.0.0-rc.1-28164352.ad7c010, @vueuse/motion/nuxt@2.0.0, nuxt-calendly@0.1.14\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\ninstall nuxt 3.7 and compared render blocked resources to 3.6.5\n\n### Describe the bug\n\nSo this is not technically a bug and sorry if this is the wrong place to report this. \r\n\r\nI noticed that TBT went up on the new nuxt version. This seems to be the case because the new version is adding quite a lot of components as render blocking resources, where previously these same resources where non blocking resources\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3231,3232,3233,3234,3235],{"name":3156,"color":3157},{"name":3140,"color":3141},{"name":3178,"color":3163},{"name":3165,"color":3166},{"name":3180,"color":3181},22995,"increased render blocking queue from nuxt 3.6.5 to 3.7","2023-09-21T08:46:46Z","https://github.com/nuxt/nuxt/issues/22995",0.7323373,{"description":3242,"labels":3243,"number":3246,"owner":3146,"repository":3146,"state":3147,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\r\n\r\nI want to use Nuxt 3 as a library in node to generate a static site for an offline PWA. I've used Quasar, but I'm new to Nuxt. \r\n\r\nNuxt/Nitro has many features I won't use. I'm very interested in Nuxt's feautures like layers, virtual file systems, module systems, and the Nuxt UI modules. \r\n\r\n----\r\n\r\nI tried to get the [programmatic usage](https://nuxt.com/docs/api/kit/programmatic) working with Javascript. \r\n\r\nI fumbled with some typescript configurations but I couldn't get the right tsconfig.json. I've read all the Nuxt docs on this I can find - is there a working example of programmatic usage I'm missing? Thank you\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/MichaelJCole/nuxt-programmatic-usage-javascript\r\n\r\nThe .nuxt folder is what Nuxt generated from the out of memory crash.\r\n\r\n### Describe the bug\r\n\r\nThe bug is that `build(nuxt)` doesn't appear to use the configuration passed. For example `.nuxt` should be `buildDir`. \r\n\r\nAlso the warnings don't appear when I run [build from the command line instead of programmatically](https://github.com/MichaelJCole/vite-pwa-nuxt-webmanifest-404). \r\n\r\nUnfortunately, it runs out of memory before completion. I checked in the generated `.nuxt` folder.\r\n\r\n```\r\n> $ node index.js ⬡ 18.18.0 \r\n--------------------------------------> options {\r\n dev: false,\r\n ready: true,\r\n rootDir: '/home/michael/nuxt/programmatic-usage/rootDir',\r\n config: {\r\n rootDir: '/home/michael/nuxt/programmatic-usage/rootDir',\r\n devtools: { enabled: true },\r\n ssr: false,\r\n buildDir: '/home/michael/nuxt/programmatic-usage/buildDir',\r\n generate: { routes: [Array] }\r\n }\r\n}\r\n--------------------------------------> loadNuxt complete\r\n\r\n[11:48:52 AM] WARN 'manifest-route-rule' middleware already exists at '/home/michael/nuxt/programmatic-usage/node_modules/nuxt/dist/app/middleware/manifest-route-rule'. You can set override: true to replace it.\r\n\r\n\r\n WARN Overriding NuxtWelcome component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtLayout component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtErrorBoundary component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding ClientOnly component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding DevOnly component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding ServerPlaceholder component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtLink component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtLoadingIndicator component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtImg component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\n\r\n WARN Overriding NuxtPicture component. You can specify a priority option when calling addComponent to avoid this warning. 11:48:52 AM\r\n\r\nℹ Building client... 11:48:52 AM\r\nℹ vite v4.5.0 building for production... 11:48:52 AM\r\ntransforming (1) node_modules/nuxt/dist/app/entry.js\r\n\u003C--- Last few GCs --->\r\n\r\n[104212:0x66c26f0] 20883 ms: Mark-sweep 3882.9 (4134.0) -> 3876.9 (4129.8) MB, 1116.9 / 0.0 ms (average mu = 0.139, current mu = 0.017) allocation failure; scavenge might not succeed\r\n[104212:0x66c26f0] 21999 ms: Mark-sweep 3885.4 (4137.1) -> 3881.2 (4134.1) MB, 1103.2 / 0.0 ms (average mu = 0.079, current mu = 0.011) allocation failure; scavenge might not succeed\r\n\r\n\r\n\u003C--- JS stacktrace --->\r\n\r\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\r\n 1: 0xb87bc0 node::Abort() [node]\r\n 2: 0xa96834 [node]\r\n 3: 0xd687f0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]\r\n 4: 0xd68b97 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]\r\n 5: 0xf462a5 [node]\r\n 6: 0xf471a8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]\r\n 7: 0xf576b3 [node]\r\n 8: 0xf58528 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]\r\n 9: 0xf32e8e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]\r\n10: 0xf34257 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node]\r\n11: 0xf147a0 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node]\r\n12: 0xf0bd6c v8::internal::FactoryBase\u003Cv8::internal::Factory>::AllocateRawArray(int, v8::internal::AllocationType) [node]\r\n13: 0xf0bee5 v8::internal::FactoryBase\u003Cv8::internal::Factory>::NewFixedArrayWithFiller(v8::internal::Handle\u003Cv8::internal::Map>, int, v8::internal::Handle\u003Cv8::internal::Oddball>, v8::internal::AllocationType) [node]\r\n14: 0x10bb952 [node]\r\n15: 0x10bbc15 [node]\r\n16: 0x12cab1b v8::internal::Runtime_GrowArrayElements(int, unsigned long*, v8::internal::Isolate*) [node]\r\n17: 0x170a079 [node]\r\n[1] 104212 IOT instruction (core dumped) node index.js\r\n```\r\n\r\n### Additional context\r\n\r\nindex.js\r\n\r\n```\r\nclass ProgrammaticUsage {\r\n async generateSite() {\r\n const { resolve } = await import(\"path\");\r\n const { build, loadNuxt } = await import(\"nuxt\");\r\n const { defineNuxtConfig } = await import(\"nuxt/config\");\r\n\r\n let nuxt = undefined;\r\n\r\n const config = defineNuxtConfig({\r\n rootDir: resolve(__dirname, \"rootDir\"),\r\n devtools: { enabled: true },\r\n ssr: false,\r\n buildDir: resolve(__dirname, \"buildDir\"),\r\n generate: { routes: [\"/\"] },\r\n });\r\n const options = {\r\n dev: false,\r\n ready: true,\r\n rootDir: resolve(__dirname, \"rootDir\"),\r\n config,\r\n };\r\n console.log(\"--------------------------------------> options\", options);\r\n\r\n if (!nuxt) nuxt = await loadNuxt(options);\r\n await nuxt.ready(); // Necessary?\r\n console.log(\"--------------------------------------> loadNuxt complete\");\r\n\r\n await build(nuxt);\r\n console.log(\"--------------------------------------> build complete\");\r\n }\r\n}\r\n\r\nconst p = new ProgrammaticUsage();\r\np.generateSite();\r\n```\r\nrootDir/nuxt.config.ts\r\n```\r\n// https://nuxt.com/docs/api/configuration/nuxt-config\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n ssr: false,\r\n modules: [\"@vite-pwa/nuxt\"], // https://vite-pwa-org.netlify.app/frameworks/nuxt\r\n pwa: {\r\n /* your pwa options */\r\n },\r\n generate: {\r\n routes: [\"/\"],\r\n // TODO https://vite-pwa-org.netlify.app/frameworks/nuxt#prompt-for-update-and-offline-ready\r\n },\r\n});\r\n```\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3244,3245],{"name":3156,"color":3157},{"name":3140,"color":3141},24197,"Javascript - build(nuxt) doesn't appear to use passed configuration","2023-11-08T21:19:47Z","https://github.com/nuxt/nuxt/issues/24197",0.7331252,{"labels":3252,"number":3255,"owner":3146,"repository":3146,"state":3147,"title":3256,"updated_at":3257,"url":3258,"score":3259},[3253,3254],{"name":3156,"color":3157},{"name":3140,"color":3141},13506,"\u003Ccomponent> seems to be broken.","2023-01-19T16:58:02Z","https://github.com/nuxt/nuxt/issues/13506",0.73316884,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4wekaxEo_2mUbaE3rcwnMIlKnT21pP0VE2b2La8yzVI":-1},"/nuxt/nuxt/26555"]