feature: add support for nodejs14.x

[adikari]

Description

AWS Lambda now supports nodejs14.x. Updated the package to support this version.

Motivation and Context

Without this support, an error is thrown when trying to run serverless offline on projects that use node 14.

How Has This Been Tested?

I made changes to the config file in serverless-offline. Then used yarn link to link the local package and used it in one of my nodejs 14 serverless projects. It did not throw an error after the changes and ran the code as expected.

Screenshots (if appropriate):

[XuluWarrior]

Does this also require an additional docker test?
e.g. https://github.com/dherault/serverless-offline/tree/master/tests/integration/docker/nodejs/nodejs12.x

[frozenbonito]

Blocked by lambci/docker-lambda#329.

[bryanvaz]

@frozenbonito is there a way to put this on a @next package pending a node14 version of lambci?

It looks like lambci is going to be a while, and serverless-webpack just added node14 support as well. (They also don't use lambci for integration tests, which is a concern for another day)

Funny thing is that I deployed on node14 yesterday and it worked without any issue, only this afternoon when testing did I realized serverless-offline had this check. 🤣 so lol for doing things out of order.

[frozenbonito]

@bryanvaz Sorry, I don't have permission to release this npm. Only reviews and merges.

[bryanvaz]

okay dokey @frozenbonito. Since it's for development, I'm sure we can all use whatever branch you want to throw the update on in the mean time.

[frozenbonito]

I made that using nodejs14.x runtime and --withDocker option will output warning and throw error.

Thank you for your contribution @adikari, I'll merge this PR.

[harishreddy-m]

When can we expect the next release along with this fix?

[adikari]

when are we releasing this? I am having to use local yarn link for now :(

[claylevering]

👍🏻 to requesting this release sooner than later

[QAnders]

It would be really nice to get this in... Had to manually add it to be able to continue local testing/dev... Thanks!

[claylevering]

As a note to anyone else that might do similar, I hacked a workaround by using a stage variable on my runtime:
runtime: ${self:custom.runtime.${self:custom.stage}}

This lets dev be 12.x (weird) but prod be 14.x

[ilionic]

Please release this version.

[nfantone]

Any movement here? What's the hold up? Something we could help with?

[restapisolutions]

I need this in release... No... I needed it a week ago.
Any workarounds?
Since it's only for development, should I clone, build and yarn link the master into my project?

[bryanvaz]

I need this in release... No... I needed it a week ago.
Any workarounds?
Since it's only for development, should I clone, build and yarn link the master into my project?

Try running this snippet, it should help solve your problem:

if (serverlessOffline.release().releaseDate < Date.now()) {
  if (Wallet.hasMonies()) {
    await serverlessOffline.sponsor(wallet: Wallet.authorize());
  } else {
    Github.fork(repo: 'serverless-offline');
  }
}

[hitwill]

Here is a temp fix that worked for me:

const isRunningLocally = !process.env.AWS_EXECUTION_ENV;
...
runtime: isRunningLocally ? "nodejs12.x" : "nodejs14.x" 

You change the runtime based on AWS environment variables that aren't available locally

[omar-dulaimi]

Hello, I'm getting the:

offline: Warning: found unsupported runtime 'nodejs14.x' for function 'graphql'
node_modules/serverless/lib/classes/CLI.js:349
offline: Failure: Unsupported runtime
node_modules/serverless/lib/classes/CLI.js:349
Error: Unsupported runtime

Any fixes for that?

[bboure]

Any chance of getting a release including this fix soon?

Thank you!