Dynamically Set Node runtime version (nodejs, nodejs4.3 or nodejs6.10) ?

[jruts]

Recently AWS launched nodejs 4.3.2 for lambdas. Since this is a public package we want the user to choose the runtime version they prefer, but default it to a specific version (preferably the latest one).

[nelsonic]

@jruts I think we should just default to 4.3 and if anyone else using dpl wants to use v0.10.36 (i.e. "Legacy" node) they can ask us for it.

[nelsonic]

@jruts any objections to me updating the runtime to nodejs4.3
as per: https://aws.amazon.com/blogs/compute/node-js-4-3-2-runtime-now-available-on-lambda/ ?

[steveoh]

What about being able to choose the different versions of node?

[nelsonic]

@steveoh good question! we could easily configure this in the package.json "engines" field: https://docs.npmjs.com/files/package.json#engines
and then set it on the lambda accordingly.

[nelsonic]

Given that Node.js v12 (LTS) is now the default and should be supported until 2022,
I feel that dynamically setting the Node.js version is no longer needed.

Closing. (feel free to re-open if you feel the requirement is still valid) 👍

[nelsonic]

Updating to Node.js v20 which is LTS until 2025: #85