Npm start error logging analysis npm-debug.log

  node.js, question
0 info it worked if it ends with ok
1 verbose cli [ 'D:\\nodejs\\node.exe',
1 verbose cli   'D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@2.14.2
3 info using node@v4.0.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart login-panli-demo@0.1.0
6 verbose unsafe-perm in lifecycle true
7 info start login-panli-demo@0.1.0
8 verbose unsafe-perm in lifecycle true
9 info login-panli-demo@0.1.0 Failed to exec start script
10 verbose stack Error: login-panli-demo@0.1.0 start: `npm run build && npm-run-all --parallel server watch:**`
10 verbose stack Exit status 1
10 verbose stack     at EventEmitter.<anonymous> (D:\nodejs\node_modules\npm\lib\utils\lifecycle.js:214:16)
10 verbose stack     at emitTwo (events.js:87:13)
10 verbose stack     at EventEmitter.emit (events.js:172:7)
10 verbose stack     at ChildProcess.<anonymous> (D:\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
10 verbose stack     at emitTwo (events.js:87:13)
10 verbose stack     at ChildProcess.emit (events.js:172:7)
10 verbose stack     at maybeClose (internal/child_process.js:817:16)
10 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
11 verbose pkgid login-panli-demo@0.1.0
12 verbose cwd E:\zan\www\panli\login-panli-demo
13 error Windows_NT 6.1.7601
14 error argv "D:\\nodejs\\node.exe" "D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
15 error node v4.0.0
16 error npm  v2.14.2
17 error code ELIFECYCLE
18 error login-panli-demo@0.1.0 start: `npm run build && npm-run-all --parallel server watch:**`
18 error Exit status 1
19 error Failed at the login-panli-demo@0.1.0 start script 'npm run build && npm-run-all --parallel server watch:**'.
19 error This is most likely a problem with the login-panli-demo package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error     npm run build && npm-run-all --parallel server watch:**
19 error You can get their info via:
19 error     npm owner ls login-panli-demo
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]

Log error as above;

"scripts": {
    "build": "npm-run-all build:**",
    "start": "npm run build && npm-run-all --parallel server watch:**",
    "test": "karma start",
    "test:coverage": "KARMA_ENV=coverage karma start --reporters coverage,coveralls",
    "test:lint": "eslint src/**/*.js*",
    "watch:test": "karma start --no-single-run --browsers Chrome",
    "pretest": "npm run test:lint",
    "prebuild": "rimraf www && mkdirp www",
    "prestart": "npm run prebuild",
    "build:static": "cpx \"examples/static/**/*\" www",
    "watch:static": "npm run build:static -- -w",
    "build:js": "webpack",
    "watch:js": "npm run build:js -- --watch",
    "build:css": "npm run watch:css -- --no-watch",
    "watch:css": "autoless --source-map examples www",
    "build:dist": "babel src --out-dir dist",
    "watch:dist": "npm run build:dist --- --watch",
    "server": "live-server ./ --port=4240"
  },

Configuration environment as above

It seems to be a problem of login-panli-demo@0.1.0, you can go to github homepage to see if there are related issues. In addition, there is nothing about this in logdetailedInformation.

19 error Failed at the login-panli-demo@0.1.0 start script 'npm run build && npm-run-all --parallel server watch:**'.
19 error This is most likely a problem with the login-panli-demo package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error     npm run build && npm-run-all --parallel server watch:**
19 error You can get their info via:
19 error     npm owner ls login-panli-demo
19 error There is likely additional logging output above.

Added to  Apr 1,2017

It seems that some children’s shoes are unhappy when they are stepped on.

Share your personal search experience on technical issues.

Google Search-Close to Correct Answer

This is a cliche. There is no denying that Google is much more powerful than Baidu /360/ sogou in terms of search technology. Why? First of all, most of our programs are based on various programming languages in the English world, and their original users (programmers) are generally foreign. While foreign programmers generally use google, there is no doubt that, so the latest problems will be found from abroad first, so google will find the latest and most reliable solutions.

Technical site

Google search is only the first step, and most of the time, the correct answer will focus on the following two places.

stackoverflow

A large number of excellent answers once witnessed a Daniel answering a technical question that he thought was very superficial, and his posture was very domineering.
 
 I summarized the gold content ranking of various answers.
  • Experts

We can always start from theory, such as various industry norms, such ashtml5 specification, then comment on various implementations, and finally give a compatible solution. This kind of answer is worth collecting.

  • Master

Be familiar with various solutions and certain principle descriptions, and generally match online demo, such as jsbin. I also like this kind of answer very much.

  • dab

Familiar with some reliable scheme, but generally will not tell you the principle, or will not, or do not understand.

  • Passers-by

I will tell you a scheme that I have tried before, which may not work well and may have some enlightening effect.

Daniel blog

Daniel usually passed the problems you encountered earlier. . .

Unless you immerse yourself in this technique for a little longer, it is difficult for you to distinguish between real Daniel and fake Daniel. Generally speaking, it can be judged from the project quality and the answer quality. If you have one or two books, you will get extra points (if you learn xxx in a few days, don’t show it out). The activity of the community is meaningless, and there are many fake Daniel who brush the sense of existence.

Github issue

There are many open source projects that have issue lists on github. Perhaps the problems you encounter have just been solved or are currently being solved. You might as well check them out.

That’s all.