the reason we haven't updated this is that ipx v3 caused a number of regressions when deploying (i.e missing sharp binaries) and @pi0 is planning to investigate or make some changes in nitro that will enable the upgrade - in particular, relying on wasm IIRC.

@danielroe
Ah, i see. I'll close the PR then.

Thank you for the information! 🍻

I'm guessing the missing binaries issue is because of --omit=optional in npm as the sharp binaries with the latest upgrade are marked as optional, so a production deployment will break if it uses --omit=optional which is a bit of a shame

But the workaround in this case is to make it a major here as well and document that the binary needed needs to be required either in the package.json or installed in a separate command after --omit=optional like npm install @img/sharp-linux-x64

I guess package managers need a new feature with basically 2 layers of optional packages, basically the really optional and the required optional which simply should not be installed if cpu and os fields don't match

Or maybe we can make a package with a postinstall that installs the optionals with cpu and os fields if it detected a npm install was run with --omit=optional and have sharp require this package

Edit: I just tried myself overriding deps and
For the case of nuxt, it seems @vercel/nft and the trace util does the job, it includes all the binaries for linux)

And you can exclude musl using nitro.externals.traceOptions

      traceOptions: {
        ignore: (path) => path.includes('linuxmusl-x64'),
      },