Jan

@DmitriyKabanov I did a research and to support this properly, we would need to create Edge Lambda that would handle renaming headers and forwarding them. It's quite unfortunate as I'm...

That sounds like something that can be done by many different ways. For example: - if you are using API call, send hostname from client in request, - if you...

Interested in this as well. This binary is Graviton compatible, but requires Fuse, which is probably not going to have access to underlying functions in Lambda.

Error seems pretty clear `Error: Invalid version number: 18`. You are no `.nvm/versions/node/v21.0.0`

``` npm ERR! sharp: Downloading https://github.com/stechstudio/libvips-lambda/releases/download/v1.0.1/libvips-8.5.5-lambda.tar.gz/v8.14.4/libvips-8.14.4-linux-arm64v8.tar.br npm ERR! sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies npm ERR! sharp: Installation error: Prebuilt libvips 8.14.4 binaries are not yet available for linux-arm64v8...

Well, it seems WSL-related I think. Either way, I would recommend changing the `--arch` flag to x86 and subsequently change architecture of image optimiser in CDK. @khuezy would it make...

@khuezy it's okay-ish, but there is overhead of starting up Next on image request. Also, trying to separate it efficiently and/or handle dependencies is rather painful. The API is rather...

Seems like gyp failing? Can you try running 'npm install sharp'?

> I faced this issue today, I just found a workaround for this: copy .next/static to .next/standalone/.next/static Can confirm, works with Next 13 for me.

Related to #8650