Default @nuxt/image bundle size #2250
Unanswered
AloisSeckar
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, today I made an observation, that surprised me (and I am not sure whether it should or it is a well known fact):
Adding
@nuxt/imageas a module into Nuxt project is significantly inflating the output server bundle size.Fresh Nuxt 4.4.5 from starter template is:
Just adding
modules: ['@nuxt/image']- and not even doing anything in code - turns it into:I believe it is because the
sharpruntime foripx, the default image provider, is being attached.I understand, that it is proably not possible to do it in some other way (apart from changing provider, but then you need an account and stuff which makes things a bit more complicated. But I still think this is some serious "bloat", eventhough it is server-side code. Or do I overreact?
DId I miss something in the docs talking about this behavior? I am aware of this part, but this sounds that it will make the problem even worse with multiple runtimes bundled...
Beta Was this translation helpful? Give feedback.
All reactions