Jimp: Jimp callback doesn't finish in AWS lambda

[SomeNerdNamedSteve]

I have been trying to get Jimp to run in a lambda function. When I try to push it to a lambda function, I don't get the Jimp image. I get <Jimp pending... >. My guess is the callback never finished. Why does a callback finish im a local machine for this library and not AWS lambda?

[edi9999]

How long do you let your lambda functions run ? Lambda functions are usually limited to 500ms, and Jimp might take longer than that.

[steffkelsey]

Why use this in AWS Lambda? Would be easier to either use ImageMagick or OpenCV, depending on what image processing you need to do. There's quite a bit more support for those libs and they are much much more mature.

[dcworldwide]

My motivation is because there are no native deps. That makes lambda deployments easier.

[hipstersmoothie]

@dcworldwide @SomeNerdNamedSteve can i see your code? I suspect you are doing something like

const image = new Jimp(...) //runs async code so . image might be undefined 
console.log(image)

change to

const image = await Jimp.read(...)
console.log(image) // should have resolved image

[hipstersmoothie]

@SomeNerdNamedSteve Any updates?

[hipstersmoothie]

@SomeNerdNamedSteve this will be closed in a month if no update is given

[hipstersmoothie]

Closed due to inactivity.