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.

npm run all error

See original GitHub issue

Describe the Bug

npm ERR! missing script: build

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alexey/.npm/_logs/2019-08-20T13_43_31_772Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! camunda-modeler-builder@0.0.0 client:build: `(cd client && npm run build)`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the camunda-modeler-builder@0.0.0 client:build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alexey/.npm/_logs/2019-08-20T13_43_31_806Z-debug.log
ERROR: "client:build" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! camunda-modeler-builder@0.0.0 build: `run-s client:build "build:distro -- {@}" "build:test-distro -- {@}" --`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the camunda-modeler-builder@0.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alexey/.npm/_logs/2019-08-20T13_43_31_870Z-debug.log
ERROR: "build --" exited with 1.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! camunda-modeler-builder@0.0.0 all: `run-s clean lint test "build -- {@}" --`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the camunda-modeler-builder@0.0.0 all script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alexey/.npm/_logs/2019-08-20T13_43_31_920Z-debug.log

Steps to Reproduce

git clone https://github.com/camunda/camunda-modeler.git
cd camunda-modeler
git pull
npm install
npm run all

Expected Behavior

All scripts finished without any exceptions and modeler launched

Environment

OS: Ubuntu 18.04
Camunda Modeler Version: 3.2.3 develop branch
Npm: 6.10.3
Node: 12.8.1

Issue Analytics

State:
Created 4 years ago
Comments:17 (6 by maintainers)

Top GitHub Comments

1reaction

AlexeyZabolockyicommented, Aug 21, 2019

problem is faded away, thank you. bye

1reaction

AlexeyZabolockyicommented, Aug 21, 2019

log.txt add info file may be it will clarify situation for you.

Top Results From Across the Web

"npm-run-all" Is Not Recognized As an Internal or External ...

If error is still present, follow these steps: Remove node_modules folder: run rm -rf node_modules; Install all dependecies: run npm i.

npm-run-all command - GitHub

A CLI tool to run multiple npm-scripts in parallel or sequential. ... -c, --continue-on-error - Set the flag to continue executing other/subsequent tasks ......

'npm-run-all' is not recognized as an internal or external ...

The error "'npm-run-all' is not recognized as an internal or external command, operable program or batch file" occurs when we forget to install...

npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.. Latest version: 4.1.5, last published: 4 years ago.

npm-run-all - npm

We can use --continue-on-error option to ignore errors. ... npm-run-all stops subsequence when a task exited with non-zero code by default. But ...