IPX provider not working properly when the default provider is not IPX

[mupinnn]

I have custom provider (thumbor) as my default provider in the config and in some case I still need IPX provider, so I pass provider props in the NuxtImg components as <NuxtImg provider="ipx" /> and the result is 404. _ipx path is not found.

The config I had:

image: {
  ipx: {},
  provider: "thumbor",
  providers: {
    thumbor: { ... }
  }
}

When I omit the ipx property, it throw Unknown provider: IPX error. The config works when I replace the default provider with ipx.

Is it expected behavior?

I create a minimal reproduction using ipx and unsplash provider to suit my problem: https://stackblitz.com/edit/nuxt-image-ipx-repro?file=app.vue

Thank you!

[Tofandel]

I have a very similar issue, I'm trying to instantiate 2 ipx instances but only one is ever setup

With a bit of debug, that's because the providerSetup is made using the name of the provider instead the provider key of the provider

const setup = input.setup || providerSetup[input.name];

Your issue is part of this because there is some hardcoding to setup ipx

if (!options.provider || options.provider === "ipx" || options.provider === "ipxStatic") {
// Setup ipx

I'll solve it in the same PR

[MickL]

I also cant use ipx as a secondary provider. I use cloudflare as my main provider for images hosted on Cloudflare Images but I want to use ipx occasionally for static images:

Nuxt config:

image: {
    provider: 'cloudflare',
}

Component:

<NuxtImg src="/static-image.jpg" provider="ipx" />

Error:

[nuxt] [request error] [unhandled] [500] Unknown provider: ipx

Did you guys find a workaround?

[nathanchase]

I found this out recently as well.

If I have this in my nuxt.config:

image: {
   provider: import.meta.env.NUXT_PUBLIC_IMAGE_PROVIDER,
}

it doesn't matter what I set that env var to - ipx will never run or work correctly in production.

If I do this instead:

image: {
   provider: import.meta.env.NUXT_PUBLIC_IMAGE_PROVIDER || 'ipx',
}

then that seems to signal to the production build that ipx is needed, and then it seems to actually install what's necessary to have ipx running on the built production server.

[MickL]

Is there any news on this? @danielroe