Sam build fails with: Build Failed Error: NodejsNpmBuilder:NpmPack - NPM Failed: npm ERR! code Z_DATA_ERROR

Question

I'm learning how to create lambdas on aws. I'm following this official tutorial.

The commands I run:

sam init (default values for everything, I'm choosing template 8 - webapp backend)

cd sam-app

sam build

The output I'm getting is:

Building codeuri: /home/sam-app runtime: nodejs14.x metadata: {} functions: ['getAllItemsFunction', 'getByIdFunction', 'putItemFunction']
Running NodejsNpmBuilder:NpmPack

Build Failed
Error: NodejsNpmBuilder:NpmPack - NPM Failed: npm ERR! code Z_DATA_ERROR
npm ERR! errno -3
npm ERR! zlib: invalid distance too far back

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/username/.npm/_logs/2021-05-20T14_02_59_425Z-debug.log

node version: 16.2.0

npm version: 7.13.0

sam version: 1.23.0

zlib version: 1:1.2.11-4

I'm not modifying any files - they're all generated by sam.

Please help to share your template file – Ashok May 20 '21 at 18:38 — Ashok, May 20 '21 at 18:38
did you find a way to solve your problem? – jhuamanchumo Jun 18 '21 at 18:58 — jhuamanchumo, Jun 18 '21 at 18:58
I've stopped using amazon sam, and started using serverless – aurelia Jun 21 '21 at 04:00 — aurelia, Jun 21 '21 at 04:00

score 7 · Answer 1 · answered Jun 24 '21 at 09:28

7

Try building this in a container. Use sam build -u

This worked for me, but I am not sure why it wouldn't build without this.

answered Jun 24 '21 at 09:28

Mark Hayward

133
5

It's the worst. It works... but why? This keeps me up at night. – Tom Scanlan Aug 31 '23 at 02:20

score 3 · Answer 2 · answered Jun 29 '21 at 13:11

3

I had the same problem in wsl2, I have solved it by installing a newer version of nodejs(v14.17.1) with nvm https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl https://github.com/nvm-sh/nvm#git-install

answered Jun 29 '21 at 13:11

Luis Encina

51
3

This worked for me. I'm assuming that I had incompatible version of node and npm. Running nvm install node updated both to the latest version. – kaifong Jan 18 '22 at 11:37

score 3 · Answer 3 · edited Mar 07 '22 at 06:00

3

I was having the same issue. I fixed it by the npm init command inside the lambda folder that we create for individual lambda functions. This will fix the version by creating the package.json.

edited Mar 07 '22 at 06:00

Dharman

30,962
25
85
135

answered Mar 07 '22 at 05:54

sahil pradhan

35
3

Worked like a charm – Roelof Briers Jun 25 '23 at 20:00

score 0 · Answer 4 · answered May 20 '21 at 18:40

0

Maybe in your template file, you might be using the below type

Type: AWS::Lambda::Function

If that's the case then change the type to below one

Type: AWS::Serverless::Function

answered May 20 '21 at 18:40

Ashok

3,190
15
31

score 0 · Answer 5 · answered Jun 18 '22 at 11:18

I suspect you're affected by https://github.com/aws/aws-sam-cli/issues/3965 which in turn is probably related to a zlib 1.2.11 problem that should be fixed by updating to use zlib 1.2.12

I've encountered this on both Fedora 36 and Arch Linux.

As Mark suggested you could probably work around it by using a container for the build. This is done by adding -u to the args for sam build.

Depending on which distro you're using you may be able to update zlib.

Note that if you are on Fedora the zlib update may take a while:

Sam build fails with: Build Failed Error: NodejsNpmBuilder:NpmPack - NPM Failed: npm ERR! code Z_DATA_ERROR

5 Answers5

Linked