Archived Forum Post

Index of archived forum posts


Node.js Module Version Mismatch on Lambda AWS

Sep 07 '16 at 14:31

We are interested in purchasing your ZIP component for our development team. We have seen positive comments about the speed and efficiency of your component so we want to use it to run an AWS Lambda function that ZIPs or appends files to a ZIP target in S3. In our tests using node in the lambda environment we run into what appear to be version errors.

Do you have anyone using the ZIP component with the Lambda / Node environment? Do you have any sample code or instructions for this specific environment?

Programmers comments follow:

To test chilkatsoft with lambda I did the following:

1 - I used a virtual machine under Linux, and I created a 'deployment package' (Lambda way of doing things)

2 - I uploaded the above to AWS.. and run a Lambda test. An error appeared - "Module version mismatch. Expected 46, got 48."

Full error stack

  "errorMessage": "Module version mismatch. Expected 46, got 48.",
  "errorType": "Error",
  "stackTrace": [
    "Object.Module._extensions..node (module.js:434:18)",
    "Module.load (module.js:343:32)",
    "Function.Module._load (module.js:300:12)",
    "Module.require (module.js:353:17)",
    "require (internal/module.js:12:17)",
    "Object.<anonymous> (/var/task/z.js:12:23)",
    "Module._compile (module.js:409:26)",
    "Object.Module._extensions..js (module.js:416:10)",
    "Module.load (module.js:343:32)"


It seems that the version of Node.js that your code is using (on AWS Lambda)is a version that corresponds to NODE_MODULE_VERSION 46.

Node Module Version 46 corresponds to Node.js versions 4... See

Therefore, you'll want to use Chilkat for Node.js 4.. If you go to, search for "chilkat". ( )

You'll see different downloads based on Node.js version (4.., 5.., or 6..) and operating system. Assuming it's for 64-bit Linux, choose

I hope that helps..