I was running email@example.com in lambda functions. Yesterday it stopped working for new builds.
Build and deploy is successful, but in runtime I get the following error:
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
The only thing that seem to change is @netlify/build. Last working version was 20.3.0. It doesn’t work on 20.3.1 and 25.0.1. I tried with both Ubuntu versions. I am using NodeJS v16.13.1. site: angry-galileo-b69b23.netlify.app
Any idea what might break things? Is it possible to set @netlify/build version?
Unfortunately that is not possible without losing required functionality. Older version results in less than 50 mb.
It doesn’t look like a problem with chrome-aws-lambda because older cached builds still work.
Is it possible to change @netlify/build version?
Under Site settings > Build & deploy > Continuous Deployment > Build image selection you can choose between the Xenial and Focal build images. You can also change the node version used in a build image.
However, this is possible more to do with the node version used to build functions which is (potentially) different to that used used in the build image. This node version is controlled via the AWS_LAMBDA_JS_RUNTIME environment variable and accepts nodejs10.x, nodejs12.x, and nodejs14.x as per this documentation.
On 13 December, node 14 became the default for functions, which may explain the issues you are seeing