Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Build from git make does not work

See original GitHub issue

It looks like instructions for building are not working anymore. I tried to update to 5.5 and it doesnt make.

Environment

chrome-aws-lambda Version: 5.5.0
OS: macos 10.15.7
Node.js Version: 14

projects|⇒ git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \
cd chrome-aws-lambda && \
make chrome_aws_lambda.zip
Cloning into 'chrome-aws-lambda'...
remote: Enumerating objects: 35, done.
remote: Counting objects: 100% (35/35), done.
remote: Compressing objects: 100% (31/31), done.
remote: Total 35 (delta 0), reused 18 (delta 0), pack-reused 0
Receiving objects: 100% (35/35), 44.59 MiB | 18.51 MiB/s, done.
mkdir -p nodejs/node_modules/chrome-aws-lambda/
cd nodejs/ && npm install lambdafs@~1.3.0 puppeteer-core@~5.5.0 --no-bin-links --no-optional --no-package-lock --no-save --no-shrinkwrap && cd -

added 53 packages, removed 1 package, and audited 70 packages in 3s

7 packages are looking for funding
  run `npm fund` for details

3 vulnerabilities (2 low, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
/Users/pavel/projects/chrome-aws-lambda
npm pack
chrome-aws-lambda-5.5.0.tgz
tar --directory nodejs/node_modules/chrome-aws-lambda/ --extract --file chrome-aws-lambda-*.tgz --strip-components=1
tar: could not chdir to 'nodejs/node_modules/chrome-aws-lambda/'

make: *** [chrome_aws_lambda.zip] Error 1

Issue Analytics

State:
Created 3 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

2reactions

mwildehahncommented, Feb 18, 2021

Moving mkdir -p nodejs/node_modules/chrome-aws-lambda/ after npm install works

1reaction

alixaxelcommented, Mar 13, 2021

@twistypigeon Version 8 (just released) ships with set of NPM 7 compatible commands:

npm install --prefix nodejs/ lambdafs@~2.0.3 puppeteer-core@~8.0.0 --no-bin-links --no-fund --no-optional --no-package-lock --no-save --no-shrinkwrap
npm pack
mkdir -p nodejs/node_modules/chrome-aws-lambda/
tar --directory nodejs/node_modules/chrome-aws-lambda/ --extract --file chrome-aws-lambda-*.tgz --strip-components=1
rm chrome-aws-lambda-*.tgz
mkdir -p $(dir $@)
zip -9 --filesync --move --recurse-paths $@ nodejs/

Top Results From Across the Web

MINGW64 "make build" error: "bash: make: command not found"

Having it installed, just run: choco install make. When it finishes, it is installed and available in Git for Bash / MinGW.

Build is not working · Issue #3223 - GitHub

It is the problem with all the newly-created ReadTheDocs-projects. If the new git-project is loaded to old ReadTheDocs project, then it works ......

Common Build Problems - Travis CI Docs

“Could not authorize build request”, usually means that the account's subscription expired or that it ran out of build credits. “Build skipped via...

Troubleshooting Omnibus GitLab installation issues

This error is thrown when /etc/gitlab/gitlab.rb configuration file contains configuration that is invalid or unsupported. Double check that there are no typos ...

git-update-index Documentation - Git

git -update-index - Register file contents in the working tree to the index ... Do not create objects in the object database for...