Node 14 Support

[spencermize]

Hello!

I'm attempting to utilize Node 14 on AWS Lambda, but I can't seem to get the component to respect my settings. It looks like the settings might be able to be added here:

express/src/utils.js

Line 404 in 81d9840

Runtime: 'nodejs12.x',

, but I'm not sure if it's on the roadmap.

Thanks!

[jyounus]

It would be nice if there were a new version of the express component with this update.

[rrooding]

I agree

[luizramirez]

we need this to be merged ha! AWS is ending support for nodejs12 @serverless-ci

[vinnyt123]

Did anyone find a workaround to get the function to run using newer NodeJS runtime? As @luizramirez said, AWS will not allow you to update a node12 Lambda starting December 14th 2022 and this component will be totally unusable

[luizramirez]

I found a solution @vinnyt123 . Will share it later when close to a computer

[luizramirez]

@vinnyt123 you can create your own component based on the serverless express component. You can then publish your component and use it in your pipeline.

[vinnyt123]

Thanks @luizramirez, I'll give that a try

[aoyama-val]

@luizramirez
Can you explain in more detail how you do that?

I tried:

1. clone git@github.com:serverless-components/express.git
2. Edit serverless.component.yml and change name, author and org
3. npm run publish
   and got

17s › Serverless › User: arn:aws:sts::486128539022:assumed-role/sp-registry-resources-prod-serv-RegistryLambdaRole-1JVOZLOJ7BXAH/sp-registry-api-function-prod-serverlessinc is not authorized to perform: lambda:TagResource on resource: arn:aws:lambda:us-east-1:486128539022:function:sp-component-express-node18_3_0_1 because no identity-based policy allows the lambda:TagResource action