Node.js 10.x support

[mberneis]

Amazon announced that they drop support for Node8 - Switching the Node Version for the Lambda function to 10.x results in a response

{
message: "Internal server error"
}

Amazons Notice:

We are contacting you as we have identified that your AWS Account currently has one or more Lambda functions using Node.js 8.10, which will reach its EOL at the end of 2019.

> What’s happening?

The Node community has decided to end support for Node.js 8.x on December 31, 2019 [1]. From this date forward, Node.js 8.x will stop receiving bug fixes, security updates, and/or performance improvements. To ensure that your new and existing functions run on a supported and secure runtime, language runtimes that have reached their EOL are deprecated in AWS [2].

For Node.js 8.x, there will be 2 stages to the runtime deprecation process:

1. Disable Function Create – Beginning January 6, 2020, customers will no longer be able to create functions using Node.js 8.10

2. Disable Function Update – Beginning February 3, 2020, customers will no longer be able to update functions using Node.js 8.10

After this period, both function creation and updates will be disabled permanently. However, existing Node 8.x functions will still be available to process invocation events.

> What do I need to do?

We encourage you to update all of your Node.js 8.10 functions to the newer available runtime version, Node.js 10.x[3]. You should test your functions for compatibility with the Node.js 10.x language version before applying changes to your production functions.

> What if I have issues/What if I need help?

Please contact us through AWS Support [4] or the AWS Developer Forums [5] should you have any questions or concerns.

[jedsmith13]

It looks like the CustomResourceFunction is fine but that there is an issue with the image handler function. Looking at the error logs it appears that it is probably that sharp-node needs to be compiled for a specific version of Node.

I am going to need this so I will take a look and see if I can get it working and if I can I will create a PR.

[jedsmith13]

I created a pull request for this. #157

To make use of it before the changes are applied to the main build you will have to follow the example for a custom deploy in the readme. Of note make sure when you build that you do it with node 10 as the problem with sharp was that it was built for NodeJS 8, I am not entirely sure if minor version differences are an issue.

[dalen]

I tried compiling it for node10, and it seems to work well then.

[beomseoklee]

We are trying to update the solution in this year to support Node.js 10.x.

[lmontier]

Do you have any news ? (because it is almost the end of the year...)

[dscpinheiro]

Hi @lmontier,

Sorry for the delay in the response.

We are still working on the update, and we’re planning to release it before December 31st.

We’re also going to use node12 (instead of node10), since this version will be supported until April 2022 (https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-node-js-12/).

[martin]

Will the update come before Christmas? Changes at the end of the year are generally a bad idea. It would be good if the solution is ready soon so that we can use it safely and tested.

[dscpinheiro]

Hi @martin,

Yes, we're planning to release it before Christmas.

[nicosh]

@dscpinheiro , any update? christmas is coming up soon

[georgebearden]

HI All - The latest commit contains the Node updates. Please let us know if you need additional assistance.

[andidev]

@georgebearden what is the recommended way to upgrade without any downtime?

[dscpinheiro]

Hi @andidev,

You should be able to update an existing stack with the latest template (https://s3.amazonaws.com/solutions-reference/serverless-image-handler/latest/serverless-image-handler.template). That will require minimum downtime since the lambda function runtime has changed.

[vitalinfo]

@andidev it depends on what sharpJS features you are using, because 0.23.3 doesn't really compatible with 0.21.3.