Serverless-chrome: Need to update with AWS NodeJS12.x runtime

[sandaemc]

Error:

Serverless plugin "serverless-plugin-chrome" initialization errored: The "serverless-plugin-headless-chrome" plugin only supports the Node.js 6.10 or 8.10 runtimes. Your service is using the "nodejs12.x" provider.

[iocentos]

Same here.

This is from amazon
An error occurred: HelloLambdaFunction - The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions.

This is from the chrome plugin
Error: The "serverless-plugin-headless-chrome" plugin only supports the Node.js 6.10 or 8.10 runtimes. Your service is using the "nodejs12.x" provider.

[adieuadieu]

I've published [email protected] with a quickfix.

[00dev]

I'm afraid that quickfix is not enough. It's need to add elements into wrapperTemplateMap in packages/serverless-plugin/src/index.js

const wrapperTemplateMap = {
  'aws-nodejs6.10': 'wrapper-aws-nodejs.js',
  'aws-nodejs8.10': 'wrapper-aws-nodejs.js', 
  'aws-nodejs10.x': 'wrapper-aws-nodejs.js',
  'aws-nodejs12.x': 'wrapper-aws-nodejs.js',
}

[rauluranga]

same here, i got the same error as well on AWS:

The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions.

[adieuadieu]

Closing this issue as it was fixed by @evgeniyannenkov in #247.

[safv12]

I'm still getting the error but with the serverless-plugin-headless-chrome plugin:

Error: The "serverless-plugin-headless-chrome" plugin only supports the Node.js 6.10 or 8.10 runtimes. Your service is using the "nodejs12.x" provider.

[safv12]

Sorry, It was my error, I just updated to [email protected] and it works.

[link365dev]

@adieuadieu Kindly update the template also: https://github.com/adieuadieu/serverless-chrome/blob/master/examples/serverless-framework/aws/package.json

Because fresh installations are still getting the error.