Unclear how to configure `@nuxt/image` to bundle provider files in `.output` dir
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
I'm using @nuxt/image-edge with Nuxt v3.{1,2}.0 and Sanity.io as a headless-CMS-provider and would like to download all my assets from the CMS and bundle them within the .output directory - from how I understand it this library is meant to provide such functionality, but I've spent quite some time trying now and can't figure it out 🥴 anyone got a hint?
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
The issue names @nuxt/image-edge, Nuxt v3, Sanity.io, and the .output directory, but no source file or test. Start by tracing the module's provider configuration and Nuxt output behavior. Done means the supported setup for bundling provider assets is documented, or the limitation is clearly stated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt
- Domain
- frontend, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100