IPX provider results 500 error in the production using @nuxt/image ^2.1.0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
Hello there! 👋
I recently upgraded in one of my projects @nuxt/image to the newest version 2.1.0 and noticed that only in the production environment the images didn't load using the IPX provider, giving the 500 error code.
I have created minimal reproduction:
main branch uses @nuxt/image@^2.1.0, nuxt-image-2.0.0 branch uses @nuxt/image^2.0.0.
Live productions:
-
@nuxt/image ^2.1.0: https://nuxt-image-2-1-0-ipx-500-67ch57pv9-krlctrl-labs.vercel.app/ -
@nuxt/image ^2.0.0: https://nuxt-image-2-1-0-ipx-500-anpu1h2nf-krlctrl-labs.vercel.app/
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
Start by reproducing the production deployment from the linked Nuxt-Image-2.1.0-IPX-500 repository, then compare its main branch with the nuxt-image-2.0.0 branch. Check the IPX provider behavior in the two live deployments. Done means images load successfully with @nuxt/image 2.1.0 in production without the 500 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxtjs, typescript
- Domain
- backend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100