https://pulumi.com logo
#general
Title
# general
m

miniature-potato-84713

11/20/2019, 8:51 PM
I’m using a Javascript function for Lambda on Edge, with
Copy code
runtime: aws.lambda.NodeJS8d10Runtime,
but then received an email from AWS that that runtime will be obsoleted:
your AWS Account currently has one or more Lambda functions using Node.js 8.10, which will reach its EOL at the end of 2019.
So I wanted to switch to then next version but
Copy code
error TS2551: Property 'NodeJS10dXRuntime' does not exist on type 'typeof import("/.../node_modules/@pulumi/aws/lambda/i...'. Did you mean 'NodeJS6d10Runtime'
Note that
NodeJS10dXRuntime
is still documented here: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/lambda/#NodeJS10dXRuntime So I changed to using the string
"nodejs10.x"
which didn’t work
Copy code
error: aws:lambda/function:Function resource 'language-redirect' has a problem: expected runtime to be one of [dotnetcore1.0 dotnetcore2.0 dotnetcore2.1 go1.x java8 nodejs4.3 nodejs4.3-edge nodejs6.10 nodejs8.10 provided python2.7 python3.6 python3.7 ruby2.5], got nodejs10.x
and then went back to
Copy code
runtime: "nodejs8.10"
which is the one that will be obsoleted soon. So… what should I do here?
Aren't you running some very old version of
pulumi-aws
?
m

miniature-potato-84713

11/20/2019, 9:08 PM
@tall-librarian-49374, I just updated Pulumi:
Copy code
> curl -sSL <https://get.pulumi.com> | sh
=== Upgrading Pulumi v0.17.16 to v1.5.2 ===
Does that not update the modules? Should I wipe the modules folder?
t

tall-librarian-49374

11/20/2019, 9:10 PM
No, it doesn't. You need to update the npm package
@pulumi/aws
.
It's now at 1.10. Although Node10 should be there since long.
m

miniature-potato-84713

11/20/2019, 9:15 PM
I ran an
npm update
, so yes, I now see that module. Although
Copy code
> npm --version
6.11.3
t

tall-librarian-49374

11/20/2019, 9:19 PM
npm --version
shows the version of npm itself
m

miniature-potato-84713

11/20/2019, 9:20 PM
Sigh, yes.
Copy code
> node --version
v10.16.3
All good then, thank you 👍
t

tall-librarian-49374

11/20/2019, 9:21 PM
that's your node... try
npm list --depth=0