Hello! I’m using the NextjsSite construct to deploy a stack. When I

yarn deploy

, the 3 NextJS lambdas are all using Node 12.x. How can I specify a NodeJS version for these NextjsSite construct lambdas?

haha we're fixing this right now cc @Frank

Great to hear! Is there a workaround in the meantime?

unfortunately no, the fix we're doing is bumping up to node16 does that work for you? or is there a reason you need to control it specifically

That would indeed fix it.

we can get this out soon

Any idea about timeline?

I'll let frank answer that but we should be able to get it out today

Awesome, thanks!

I've been having this same issue and wanted to add that after bumping the version to node 16, I started seeing the following. Not sure if you guys have run into it @Frank @thdxr

{
  "errorType": "Error",
  "errorMessage": "Cannot find package 'aws-sdk' imported from /var/task/s3-bucket.js\nDid you mean to import aws-sdk/clients/s3.js?",
  "code": "ERR_MODULE_NOT_FOUND",
  "stack": [
    "Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'aws-sdk' imported from /var/task/s3-bucket.js",
    "Did you mean to import aws-sdk/clients/s3.js?",
    "    at new NodeError (node:internal/errors:371:5)",
    "    at packageResolve (node:internal/modules/esm/resolve:930:9)",
    "    at moduleResolve (node:internal/modules/esm/resolve:976:18)",
    "    at defaultResolve (node:internal/modules/esm/resolve:1078:11)",
    "    at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)",
    "    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)",
    "    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:79:40)",
    "    at link (node:internal/modules/esm/module_job:78:36)"
  ]
}

yeah this will be part of the fix

Awesome. Thanks!

maybe this is the fix, but any reason not to have it respect the defaults?

Yeah for the 3 user managed lambdas, we should respect the defaults. The SST managed ones, those will be updated to 16.

I deleted it, as I took another route, but that is interesting…

Updated the lambda runtime to Node 16 in

1.2.10

. And you can override it like this:

new Function(stack, "Function", {
  path: "path/to/site",
  runtime: "nodejs16.x", // nodejs12.x or nodejs14.x
})

All working now. Thanks for the fix! @Frank @thdxr