The @nuxt/image dependencies are quite heavy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
I was working on a project for my company and noticed that the build bundle size was extremely large—around 30 MB! The project itself isn’t that big. To confirm whether this was related to a specific library, I created a new Nuxt project and added the Nuxt Image library. The bundle size increased from 1.72 MB to 22 MB. I believe the library should optimize the package size. I tested this using version 1.11.0.
Without nuxt Image
With Nuxt image:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with a fresh Nuxt project using @nuxt/image version 1.11.0, comparing bundle sizes with and without the module. Then inspect the module's dependency tree to identify the source of the increase; done means reducing the package's added bundle size without breaking image optimization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100