-
Notifications
You must be signed in to change notification settings - Fork 90
"npm run build" run fail #311
Description
**Type of issue:Documentation
**Node version (for build issues): 14.15
### [stack info]:
[@ activiti-modeling-app-master]$ npm run build
activiti-modeling-app@0.2.0 prebuild /***/activiti-modeling-app-master
mkdir -p ./app/.tmp && cp ./app/src/app.config.json.tpl ./app/.tmp/app.config.json
activiti-modeling-app@0.2.0 build /***/activiti-modeling-app-master
NODE_OPTIONS=--max_old_space_size=8192 ${NG_CLI:-nx} build
nx run [project][:target][:configuration] [_..]
Run a target for a project
(e.g., nx run myapp:serve:production).
You can also use the infix notation to run a target:
(e.g., nx serve myapp --configuration=production)
You can skip the use of Nx cache by using the --skip-nx-cache option.
Options:
--version Show version number [boolean]
--prod Use the production configuration [boolean] [default: false]
-c, --configuration Target configuration [string]
--project Target project [string]
--output-style Defines how Nx emits outputs tasks logs
[string] [choices: "dynamic", "static", "stream", "stream-without-prefixes", "compact"]
--nx-bail Stop command execution after the first failed task [boolean] [default: false]
--nx-ignore-cycles Ignore cycles in the task graph [boolean] [default: false]
Error: Both project and target have to be specified
at parseRunOneOptions (//activiti-modeling-app-master/node_modules/nx/src/command-line/run-one.js:76:15)
at Object. (//activiti-modeling-app-master/node_modules/nx/src/command-line/run-one.js:20:22)
at Generator.next ()
at fulfilled (/***/activiti-modeling-app-master/node_modules/tslib/tslib.js:115:62)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! activiti-modeling-app@0.2.0 build: NODE_OPTIONS=--max_old_space_size=8192 ${NG_CLI:-nx} build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the activiti-modeling-app@0.2.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! /***/.npm/_logs/2023-02-02T10_15_13_838Z-debug.log