Open JosefHjorth opened 3 years ago
I noticed there was a similar issue reported here; https://github.com/nuxt/image/issues/215 , but I'm running 0.5.0 already
Also, people seem to get a "Generated static image" when running npm (or yarn) run generate in the console output, but I don't get that.
Is the issue with ssr: false,
? I believe the _ipx
route is a server side endpoint that does the image manipulation. Without the server running the static image provider (ipx) can't be accesses to generate the static images?
Thanks! Might be, but does that mean I can't use nuxt/image since I use client side rendering only?
I believe the @nuxt/image
static provider (ipx) requires full static setup.
You may need to consider another @nuxt/image
provider such as cloudinary to host the images and do image transformations.
Switched to cloudinary and it worked much better. Thanks.
@shadow81627 cant the IPX part be run during the generation step? like, open the server for IPX; generate the images, close it down, and then we are left with the images plus a client-only / full static generated site?
Yes, I run ipx with static target. You might need to have SSR on for the ipx server to run during generate.
So it seems that having
target: 'static'
ssr: false
breaks nuxt-image with the default provider. This also happens in 0.5.0.
Any solution besides using another provider as suggested above? I'd just like to run the ipx optimizations on generate command and have all ready in the dist folder to be moved to production :)
Any updates here?
+1
any update?
Any update? I'm running a Nuxt3 App with ssr false.
When building my solution it tries to reference the images in a missing _ipx folder.
This is my (relevant) configuration. I've tried with the default configuration, but whatever I do nuxt-image tries to reference _ipx folder.
This is the html element: `
`
Why is nuxt-image referencing non existent _ipx folder?