Open cfdxkk opened 6 months ago
Having similar issues but receiving Error: [403] IPX_FORBIDDEN_PATH
when running nuxi generate
.
Other developers report same issue here #1006
Same when deployed on Zeabur.
Any new insights on this issue? I am having the same issue on netlify.
Using nuxt generate
instead of nuxt build
"fixes" the problem.
Anyway this does not seem like a solution.
Have anyone found any solution to this? Facing similar issue, images already in public/images directory.
but not sure why vercel looking for images in static directory?
@haidertm
Have anyone found any solution to this? Facing similar issue, images already in public/images directory.
but not sure why vercel looking for images in static directory?
I gaved up, it still bug but try another inelegant way to fix.
now i use a mixing mode:
If I am sure that image must is a internet image, I will use a Custom Provider like this.
Specifically, it splices a URL and requests a resized image, so that the image processing task will be completed by a third-party provider.
<NuxtImg provider="yourProvider" src="https://cloudflare.com/foo.jpg" />
If i am sure a image use static file. I will NOT set the provider attribute.
No provider means automatic provider. So the provider will be ipx in my localhost environmentand Vercel Image Optimization in Vercel production environment.
<NuxtImg src="static/bar.jpg" />
If i don't know a image is internet or static, I will use v-if / v-else
and a Computed Properties.
<script lang="ts">
const imageUrl = ref<string>('static/baz.jpg') // This URL maybe change into a Internet image.
const isStaticImage = computed(() => imageUrl.value.startsWith('static/'))
</script>
<template>
<NuxtImg v-if="isStaticImage" :src="imageUrl" />
<NuxtImg v-else provider="yourProvider" :src="imageUrl" />
</template>
Just my 2 cents, make sure the images aren't inside ClientOnly tags, as the NuxtImg is server-side only because it crawls the image references server side and based on that, it bundles the images during nuxt generate
.
Removing ClientOnly tags fixed this same issue for me as I wrongly assumed NuxtImg can be used client side
1. Issue
Unable to read static Image files in
/public
using ipx as provider on vercel, seeing[404] [IPX_FILE_NOT_FOUND]
error.This works in both local dev and production (Vercel) environment.
This only works in local dev environment and get [404] [IPX_FILE_NOT_FOUND] error in production (Vercel) environment.
This works in both local dev and production (Vercel) environment.
2. Using
3. Minimal Reproduction
Source Code: https://github.com/cfdxkk/nuxt-image-vercel-ipx Online Demo: https://nuxt-image-vercel-ipx.vercel.app/
4. Something Maybe Useful
nuxt.config.ts
Vercel build command (nuxt default)
Source & Build Output in Vercel
Source
Build Output