How can I tree-shake reka-ui?

[phtngyn]

Description

I am using the Nuxt UI playground template from here.

After running pnpm build, I noticed that .output/server/node_modules/reka-ui/dist contains many unused components. How can I configure it to tree-shake these unused components after the build?

[qodeboy]

I can confirm this is a real problem. Official starter template when loaded loads more that 700 modules for a page with one button. This makes whole DX a nightmare - HMR lags for 3-5 seconds, fresh reloads re-downloads whole bunch of modules.

I am not sure this is nuxt-ui/reka's thing or a vite's, but this makes our flow a lot harder.

15MB of modules for a page with a button seems definitely broken.

P.S. Production builds are totally fine - components are tree-shaked and only used appears in bundle.

[gurgeous]

I see this as well.

[atinux]

This is so far an upstream issue related to Vite not treeshaking the module in development, you can refer to this issue: vitejs/vite#8237

Apparently, this will be fixed once Vite migrates to Rolldown.

[qodeboy]

This makes total sense. But the fun part is I have tried with experimental https://github.com/vitejs/rolldown-vite and found no difference at all - still tons of bundles being loaded.

But the strange part that is more likely to be related to nuxt/nuxt-ui - is why modules that are not even used on the page (in the userland code at all) are being included and served. On my screenshot you can see that i.e. AlertDialog and related components are loaded - but never used/imported in userland code.

My silly assumption was it is due to autoImports - and I have tried to completely disable it. With no luck either.

[grous0]

I also tried the Rolldown fork but no difference. Someone from the upstream Vite issue says switching to something like Rsbuild could help so i will try that #8237

[qodeboy]

Please share your findings if you can make rspack work for you, because it fails for me even on simple fresh nuxt + nuxt-ui project. Pavlo Sheiman, email: ***@***.*** вт, 8 лип. 2025 р. о 20:37 Ömer ***@***.***> пише:

…

*grousk* left a comment (nuxt/ui#3376) <#3376 (comment)> I also tried the Rolldown fork but no difference. Someone from the upstream Vite issue says switching to something like Rsbuild could help so i will try that #8237 <vitejs/vite#8237 (comment)> — Reply to this email directly, view it on GitHub <#3376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEEVXPK2GYUBD3XEYXGB5L3HQFWHAVCNFSM6AAAAABXU2WRZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANBZHE2DANJRGM> . You are receiving this because you commented.Message ID: ***@***.***>

[grous0]

Please share your findings if you can make rspack work for you, because it
fails for me even on simple fresh nuxt + nuxt-ui project.

Pavlo Sheiman,
email: @.***

вт, 8 лип. 2025 р. о 20:37 Ömer @.***> пише:
…

So Rsbuild has no compatibility for Vite plugins. I checked Rsbuild and Vite's plugin APIs and it is just very different so i can't do anything with it.

[ii517]

I was wondering if anyone has solved this problem yet?

[qodeboy]

We all are waiting for rolldown here. For my case I was able to go from ~1200 modules to ~400 modules by disabling all auto-importing crap and fine-tuning vite's optimizeDeps.

…

On Fri, Aug 15, 2025 at 5:44 AM JinyLin ***@***.***> wrote: *ii517* left a comment (nuxt/ui#3376) <#3376 (comment)> Has anyone solved this problem yet? — Reply to this email directly, view it on GitHub <#3376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEEVXO3YWOHXQBSHB5PWGL3NVJSBAVCNFSM6AAAAABXU2WRZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJQGUZDAMZZGA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Pavlo Sheiman, email: ***@***.***

[ii517]

We all are waiting for rolldown here. For my case I was able to go from
~1200 modules to ~400 modules by disabling all auto-importing crap and
fine-tuning vite's optimizeDeps.
…

On Fri, Aug 15, 2025 at 5:44 AM JinyLin @.***> wrote:
ii517 left a comment (nuxt/ui#3376)
<#3376 (comment)>

Has anyone solved this problem yet?

—
Reply to this email directly, view it on GitHub
<#3376 (comment)>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEEVXO3YWOHXQBSHB5PWGL3NVJSBAVCNFSM6AAAAABXU2WRZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJQGUZDAMZZGA
.
You are receiving this because you commented.Message ID:
@.***>

--
Pavlo Sheiman,
email: @.***

Good to know, thanks