-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: context.done is not a function #223
Comments
@tyshcr http://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-using-old-runtime.html |
I see. Thank you. I will implement |
In the newer versions of `node-lambda` the `context.suceed` and `context.done` methods have been deprecated, but we use those functions (for now) still. This pins that package to version 0.8.11, which has the functionality we need. Fixes #12 Ref: motdotla/node-lambda#223
my fault was , i forgot to use path.join while using sendFile... |
I am using Node v6.2.2 and the latest version of node-lambda.
I am able to run my lambda locally using
node-lambda run
, but if I usecontext.succeed()
orcontext.done()
I get an error in my Terminal that says:/node_modules/aws-sdk/lib/request.js:31 throw err; ^ TypeError: context.done is not a function
I found a similar issue from 2016 being discussed here #50
The text was updated successfully, but these errors were encountered: