92% chunk asset optimization Killed
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 64
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
-
I'm submitting a ...
[ ] bug report -
What is the current behavior?
npm install successfully then starting using npm start and getting below error when it reach 92%
then it is killed -
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
[root@spare frontend]# npm start
ng2-admin@1.0.0 start /root/cloudref/frontend
ng serve
** NG Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200 **
92% chunk asset optimization
Killed
-
What is the expected behavior?
Must run successfully - right now it is crash after reach 92% -
Please tell us about your environment:
node -v v6.14.2
npm -v 3.10.10
centos 7 64 bit
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported npm install and npm start commands, which invokes ng serve, on the listed Node.js, npm, and CentOS versions. Observe the build at “92% chunk asset optimization” and compare the result with a successful development-server startup. Done means npm start completes without the process being killed and serves the application on localhost:4200.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100