Error: Command failed: npm -s ci --production --no-audit --prefix /tmp/build-lambda

Open
#537 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
cli, cloud, devops

Research direction

Start by reproducing the node-lambda deploy command with a package containing npm-shrinkwrap.json, then trace the dependency-install step running npm -s ci --production --no-audit --prefix /tmp/build-lambda. Done means deployment succeeds for that package; the issue names no source file or test to update.

Written by the indexing model from the issue text.

Description

question

Hi team,
We are trying to deploy using node-lambda. We are getting below error
node-lambda deploy -a $AWS_ACCESS_KEY_ID_LABS -s $AWS_SECRET_ACCESS_KEY_LABS -n "$AWS_FUNCTION_NAME"_Test -e "" -f deploy.env -o "$AWS_ROLE_DEV"
=> Moving files to temporary directory
=> Running npm ci --production
Error: Command failed: npm -s ci --production --no-audit --prefix /tmp/build-lambda
at ChildProcess.exithandler (child_process.js:303:12)
at ChildProcess.emit (events.js:310:20)
at ChildProcess.EventEmitter.emit (domain.js:482:12)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
at Process.onexit (/var/lang/lib/node_modules/node-lambda/node_modules/async-listener/glue.js:188:31) {
killed: false,
code: 1,
signal: null,
cmd: 'npm -s ci --production --no-audit --prefix /tmp/build-lambda'
}
This issue seems to be because of npm-shrinkwrap.json. It is not able to build when the package has npm-shrinkwrap.json
Please look into this issue. Deployment is failing into production so it is very critical for us.

Dominant language
JavaScript
Stars
1.4k
Forks
185
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.