\n \u003Cp class=\"text-neutral-200 text-xs\">\n {{ transactionCost.credits }}\n \u003C/p>\n\u003C/UTooltip>\n```\n\n``` \n\u003CNuxtLayout>\n \u003CUApp :toaster=\"{ position: 'top-right' }\">\n \u003CNuxtPage />\n \u003C/UApp>\n\u003C/NuxtLayout>\n```\n\n\n### Description\n\nThe `app.vue` is already using the `UApp`. When I try to add a `UTooltip` inside the modal, it throw an error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```\nUncaught (in promise) Error: Injection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n```",[3255,3258,3260],{"name":3256,"color":3257},"bug","d73a4a",{"name":3219,"color":3259},"CB47CF",{"name":3261,"color":3262},"v3","49DCB8",2801,"ui","[v3][UTooltip] `UTooltip` inside `UModal` causing error","2025-02-06T15:28:30Z","https://github.com/nuxt/ui/issues/2801",0.7469309,{"description":3270,"labels":3271,"number":3272,"owner":3196,"repository":3273,"state":3222,"title":3274,"updated_at":3275,"url":3276,"score":3277},"#913 has resulted in my dev server, running on Windows 11, restarting every ~5 minutes due to 'fake' change notifications on `nuxt.config.ts` and `.nuxt/dist/server`, making dev mode essentially unusable.\n\nExperimentation shows that actions not involving a change to file content or modification time can result in a `'change'` event from `fs.watch`, triggering the reload. E.g., just opening file properties in Windows Explorer can cause a `'change'` event. This is sufficient to trigger a dev server restart.\n\nI'm not sure what is poking at these files every ~5 minutes, but I've verified that no actual changes have occurred when the `'change'` events are emitted, so this new strategy seems unfeasible on Windows. Explicitly rolling back to `@nuxt/cli` \u003C 3.26.0 (3.25.1, specifically) has resolved the issue for me.",[],1030,"cli","Move to native fs.watch results in unpredictable restarts","2025-09-26T13:30:20Z","https://github.com/nuxt/cli/issues/1030",0.75042105,{"description":3279,"labels":3280,"number":3287,"owner":3196,"repository":3196,"state":3222,"title":3288,"updated_at":3289,"url":3290,"score":3291},"### Describe the feature\r\n\r\nPresently Nuxt seems to lack a build cache? (_[Next has one](https://nextjs.org/docs/pages/building-your-application/deploying/ci-build-caching) that can be cached for speeding up builds_)\r\n\r\nIn a real Nuxt project, I am observering `nuxt build` taking roughly 38 seconds (_8s vite client, 11s vite server, 19s nitro server_). This does not improve when running `nuxt build` again, even though nothing has changed.\r\n\r\nIs it possible to optimize any of the build steps involved?\r\n- Do the build tools used support re-use of a cache and Nuxt just needs to expose a setting (_or document one_) for enabling this support?\r\n- If not, are there any opportunities to implement this where it'd be worthwhile?\r\n\r\nPerhaps you could use [BLAKE3](https://github.com/BLAKE3-team/BLAKE3#readme) via [`@noble/hashes`](https://www.npmjs.com/package/@noble/hashes#blake3) as a speedy way to get a checksum on build inputs? (_could be an opt-in flag_). This is perhaps a naive approach, and depending on overhead may not always help reduce the build time 馃槄 \r\n\r\n---\r\n\r\n### Reproduction / Comparison\r\n\r\nNuxt example:\r\n\r\n```console\r\n# Reproduction environment:\r\n$ docker run --rm -it --workdir /reproduction node:20-bookworm-slim bash\r\n$ corepack enable\r\n\r\n# An example project (possibly too small for measurable difference):\r\n$ npx -y nuxi init --packageManager pnpm --gitInit false .\r\n# Repeat this step, no improvement to build time:\r\n$ time pnpm build\r\n```\r\n\r\nNext.js example:\r\n\r\n```console\r\n# Reproduction environment:\r\n$ docker run --rm -it --workdir /reproduction node:20-bookworm-slim bash\r\n$ corepack enable\r\n\r\n# An example project:\r\n$ npx -y create-next-app@latest --use-pnpm --example hello-world .\r\n# Repeat this step, 1st build 10s while builds after are 5s:\r\n$ time pnpm build\r\n```\r\n\r\n---\r\n\r\n### Related\r\n\r\nI've looked through Nuxt and Nitro docs, nothing really stands out cache wise for a CI to optimize reducing future builds with. Ideally a small change (_or none at all_) should not require the full build time.\r\n\r\n> Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).\r\n\r\nFirst five pages of each for keywords searches of: `build time`, `build speed`, `build cache`:\r\n\r\n- Disabling GZIP in builds for some gain (_`sourcemaps` is another potential option_): https://github.com/nuxt/nuxt/issues/23352#issuecomment-1732026846\r\n- 4 minute build times: https://github.com/nuxt/nuxt/discussions/20642\r\n- 6 minute build times: https://github.com/nuxt/nuxt/discussions/20494\r\n- 10 minute report, with 1 minute if disabling SSR: https://github.com/nuxt/nuxt/issues/20042\r\n- 80s to 5-10s report if using `experimental.treeshakeClientOnly: false`: https://github.com/nuxt/nuxt/issues/20042#issuecomment-1495180211\r\n - https://nuxt.com/docs/guide/going-further/experimental-features#treeshakeclientonly\r\n - https://nuxt.com/docs/api/configuration/nuxt-config#treeshakeclientonly\r\n- A report of Nuxt spending half build time in nitro, but nitro direct being fast: https://github.com/nuxt/nuxt/issues/20042#issuecomment-1667765867\r\n- A suggestion that upcoming Rollup 4.0 release adopting the rust-based SWC may bring improvements: https://github.com/nuxt/nuxt/issues/20042#issuecomment-1703711265\r\n - Associated Rollup 4 PR: https://github.com/rollup/rollup/pull/5073\r\n - Rollup 4 release tracking PR: https://github.com/rollup/rollup/pull/5140\r\n- Mar 2019 **Nuxt 2** doc links for several build config options to optimize build time (_all settings tied to webpack_): https://github.com/nuxt/nuxt/issues/5131#issuecomment-468231314\r\n\r\nThere is a deployment guide, but not sure if Nuxt has one for minimizing time of production builds.\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3281,3282,3285,3286],{"name":3230,"color":3231},{"name":3283,"color":3284},"good first issue","fbca04",{"name":3190,"color":3191},{"name":3193,"color":3194},23392,"Optimize build time speed with a cache (or other settings)","2024-08-28T20:00:39Z","https://github.com/nuxt/nuxt/issues/23392",0.75408995,{"labels":3293,"number":3296,"owner":3196,"repository":3196,"state":3222,"title":3297,"updated_at":3298,"url":3299,"score":3300},[3294,3295],{"name":3230,"color":3231},{"name":3233,"color":3234},7698,"Reduce Blocking time of Nuxt Applications","2023-01-22T15:52:36Z","https://github.com/nuxt/nuxt/issues/7698",0.7541394,{"description":3302,"labels":3303,"number":3311,"owner":3196,"repository":3196,"state":3222,"title":3312,"updated_at":3313,"url":3314,"score":3315},"needs to be investigated - probably not a terribly complex fix\n\nalso `test client-side navigation` for server islands",[3304,3305,3308],{"name":3283,"color":3284},{"name":3306,"color":3307},"chore","D0F1A9",{"name":3309,"color":3310},"馃Ч p1-chore","FEF2C0",30867,"flaky test for spa-preloader","2025-03-17T22:48:40Z","https://github.com/nuxt/nuxt/issues/30867",0.75471526,["Reactive",3317],{},["Set"],["ShallowReactive",3320],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$focBK2AwueAD_fe3zxY0f9Tec0Nl7mt2_6uWjsUSehfQ":-1},"/nuxt/nuxt/25048"]