# Chrome-aws-lambda stopped working, possibly due to different version of @netlify/build **URL:** \ **Category:** Support\ **Tags:** lambda-functions\ **Created:** [December 16, 2021, 5:38pm UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847 "2021-12-16T17:38:21Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ibanic](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/ibanic/32/32346_2.png) [@ibanic](https://answers.netlify.com/u/ibanic)\ **Post date:** [December 16, 2021, 5:38pm UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/1 "2021-12-16T17:38:21Z")
I was running chrome-aws-lambda@5.5.0 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? ---
**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\ **Post date:** [December 16, 2021, 10:28pm UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/2 "2021-12-16T22:28:16Z")
Hi @ibanic According to the npm package page for [chrome-aws-lambda](https://www.npmjs.com/package/chrome-aws-lambda) the latest version is `10.1.0`. Have you tried updating to the latest version? If not, you might need to file and [issue](https://github.com/alixaxel/chrome-aws-lambda/issues) on the repository (it is not a Netlify package.) ---
**Author:** ![ibanic](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/ibanic/32/32346_2.png) [@ibanic](https://answers.netlify.com/u/ibanic)\ **Post date:** [December 17, 2021, 6:36am UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/3 "2021-12-17T06:36:38Z")
Hi, yes I have tried the latest version. It doesn’t work because compiled lambda .zip package is more than 50 mb. ---
**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\ **Post date:** [December 17, 2021, 6:52am UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/4 "2021-12-17T06:52:52Z")
Netlify builds the functions using [GitHub - netlify/zip-it-and-ship-it: Intelligently prepare Node.js Lambda functions for deployment](https://github.com/netlify/zip-it-and-ship-it) which bundles all dependencies. The outcome, in your case, is larger than that permissible by AWS. In order to deploy the function, you will need to decrease the size by reducing the dependencies it uses. ---
**Author:** ![ibanic](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/ibanic/32/32346_2.png) [@ibanic](https://answers.netlify.com/u/ibanic)\ **Post date:** [December 17, 2021, 7:24am UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/5 "2021-12-17T07:24:09Z")
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? ---
**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\ **Post date:** [December 17, 2021, 7:55am UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/6 "2021-12-17T07:55:17Z")
Under _ **Site settings \> Build & deploy \> Continuous Deployment \> Build image selection** _ you can choose between the [Xenial](https://github.com/netlify/build-image/tree/xenial) and [Focal](https://github.com/netlify/build-image/) build images. You can also change the [node version](https://docs.netlify.com/configure-builds/manage-dependencies/#node-js-and-javascript) 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`](https://docs.netlify.com/functions/build-with-javascript/#runtime-settings) environment variable and accepts `nodejs10.x`, `nodejs12.x`, and `nodejs14.x` as per [this documentation](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html). **Edit:** On 13 December, node 14 became the default for functions, which may explain the issues you are seeing > [@Functions: Node 14 will be the new default runtime](https://answers.netlify.com/t/functions-node-14-will-be-the-new-default-runtime/47224): > > As of December 13, all new Netlify Functions will use the Node 14 runtime by default. This will affect all new deploys, unless the runtime has been [manually set using the AWS\_LAMBDA\_JS\_RUNTIME environment variable](https://docs.netlify.com/functions/build-with-javascript/#runtime-settings). This will provide better support out of the box for frameworks such as Gatsby, SvelteKit and Nuxt 3, plus improved performance and access to modern Javascript features without needing to transpile your code (I recommend [optional chaining](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining)!). If for any reason your functions rely on No… ---
**Author:** ![zackseuberling](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/zackseuberling/32/10799_2.png) [@zackseuberling](https://answers.netlify.com/u/zackseuberling)\ **Post date:** [December 17, 2021, 10:29pm UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/7 "2021-12-17T22:29:59Z")
I am running into [the same issue](https://answers.netlify.com/t/lambda-function-failing-in-netlify-build-20-3-1/48900) with regards to netlify/build versions ---
**Author:** ![coelmay](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/coelmay/32/24427_2.png) [@coelmay](https://answers.netlify.com/u/coelmay)\ **Post date:** [December 17, 2021, 10:34pm UTC](https://answers.netlify.com/t/chrome-aws-lambda-stopped-working-possibly-due-to-different-version-of-netlify-build/48847/8 "2021-12-17T22:34:53Z")
I have answered on the thread you created @zackseuberling