For anyone finding this in future and still having the issue:

I am also still experiencing this in an electon project with Jimp 0.9.3 (but only when I package the app with electron-builder).

Things I tried from above which didn’t work:

# tsconfig.json
"esModuleInterop": true,
"allowSyntheticDefaultImports": true,

# package.json
"@babel/runtime": "^7.7.2",

# index.ts
require("@babel/runtime/regenerator");
import * as Jimp from 'jimp/es';

The only thing I have found which did work:

# package.json
# swap "jimp" to:
"jimp-compact": "^0.9.3"

# index.ts
import * as Jimp from 'jimp-compact';

I know that it is a semi-unofficial fork, but however jimp-compact dependency works vs jimp seems to fix the error…

@divinealpine are you able to test again but against 0.8.6-canary.815.502.0?

same here, even when using plan js with serverless-webpack downgrading back to 0.6.4 fixes the issue

🚀 Issue was released in v0.9.3 🚀

Fantastic! Thanks for checking @andrewrt! Those warnings should go away once this hits stable IIRC

I updated the import to import Jimp from "jimp"

redeployed and then invoked the lambda function and am receiving the same error message I had above.

@crutchcorn Yep, using typescript.

tsconfig.json:

{ "compilerOptions": { "esModuleInterop": true, "allowSyntheticDefaultImports": true, "sourceMap": true, "target": "es6", "lib": [ "esnext", "dom" ], "moduleResolution": "node" }, "exclude": [ "node_modules" ] }

code:

`import Jimp from “jimp/es”

export const doSomething: Handler = (event: APIGatewayEvent, context: Context) => { Jimp.read(‘https://avatars0.githubusercontent.com/u/1192452?s=88&v=4’) .then(image => { console.log(‘doing something’); }) .catch(err => { console.log('handle exception: ', err); }); … } `

More details if helpful: I’m trying to import jimp in a AWS Lambda function. Lambda function runtime is set to nodejs10.x.

Thanks for the feedback, @divinealpine. Can you show me the code you used to do imports and running?

Are you using TypeScript? (if so, what’s your tsconfig.json look like and what version are you using?)

Are you using babel?

@crutchcorn I tried using the version you have here and when I invoke my lambda function with Serverless (aws, serverless, lambda), I get a different error:

{ "errorType": "TypeError", "errorMessage": "Cannot assign to read only property 'exports' of object '#<Object>'", "trace": [ "TypeError: Cannot assign to read only property 'exports' of object '#<Object>'", " at Object.<anonymous> (/var/task/webpack:/node_modules/@jimp/core/es/request.js:34:10)", " at Object.call (/var/task/handler.js:9:283271)", " at r (/var/task/webpack:/webpack/bootstrap:19:22)", " at Module.call (/var/task/handler.js:25:14004)", " at r (/var/task/webpack:/webpack/bootstrap:19:22)", " at Object.call (/var/task/handler.js:9:310475)", " at __webpack_require__ (/var/task/webpack:/webpack/bootstrap:19:22)", " at /var/task/webpack:/webpack/bootstrap:83:10", " at Object.<anonymous> (/var/task/handler.js:1:968)", " at Module._compile (internal/modules/cjs/loader.js:778:30)" ] }

@andrewrt @RomainFallet can you test against 0.8.6-canary.815.488.0 to confirm a fix? I have tested against node-vibrant and it seems to be working for me

Same here, thanks to @vanerleo, downgrading to 0.6.4 is my workaround for now.

Related https://github.com/oliver-moran/jimp/pull/783