node-lambda - TypeError: handler is not a function

Question

New to AWS and found it quite straightforward so far but really getting stuck packaging a lambda function.

I'm using node-lambda to try and run the function but keep getting the following error on node-lambda run:

/usr/local/lib/node_modules/node-lambda/lib/main.js:93
      handler(event, context, callback);
      ^

TypeError: handler is not a function
    at Lambda._runHandler (/usr/local/lib/node_modules/node-lambda/lib/main.js:93:7)
    at Lambda.run (/usr/local/lib/node_modules/node-lambda/lib/main.js:49:8)
    at Command.<anonymous> (/usr/local/lib/node_modules/node-lambda/bin/node-lambda:89:12)
    at Command.listener (/usr/local/lib/node_modules/node-lambda/node_modules/commander/index.js:301:8)

My index.js file has the handler declared like so

exports.myHandler = function(event, context) {

And the AWS_HANDLER in my .env is set to index.handler. I eel like I'm missing an obvious step.

You've named it myHandler. You either need to name it handler or change the name that you are telling Lambda to look for. — Mark B
– Mark B, Commented May 13, 2016 at 15:18

prince Arthur · Accepted Answer · 2021-11-30 14:52:08Z

2

use exports.handler = async function(event, context) { instead of exports.myHandler = function(event, context) {

answered Nov 30, 2021 at 14:52

prince Arthur

2313 silver badges5 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

jarmod Over a year ago

FYI the AWS Lambda JS runtime didn't support async/await until April 2018, 2 years after this question was originally asked.

Collectives™ on Stack Overflow

node-lambda - TypeError: handler is not a function

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related