search

serverless-components / express

⚡ Take existing Express.js apps and host them easily on cheap, auto-scaling, serverless infrastructure (AWS Lambda and AWS HTTP API).
https://serverless.com/components
Apache License 2.0
375 stars 34 forks source link

Node 14 Support #63

Open spencermize opened 3 years ago

spencermize commented 3 years ago

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: https://github.com/serverless-components/express/blob/81d9840355efa45b4ecf46a1ea09b3eba181e8a9/src/utils.js#L404, but I'm not sure if it's on the roadmap.

Thanks!

jyounus commented 3 years ago

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

rrooding commented 3 years ago

I agree

luizramirez commented 1 year ago

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

vinnyt123 commented 1 year ago

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 commented 1 year ago

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

luizramirez commented 1 year ago

@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 commented 1 year ago

Thanks @luizramirez, I'll give that a try

aoyama-val commented 1 year ago

@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