-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install #249
Comments
这是因为npm包安装不稳定,以前也遇到过。解决办法:
另外,这个包是测试时使用的,如果执行 npm start, 服务应该可以运行的。 |
npm WARN package.json Dependency 'gulp-protractor' exists in both dependencies and devDependencies, using 'gulp-protractor@^1.0.0' from dependencies |
Administrator@WIN-9PH4ISN44NM MINGW64 /e/zan/www/node/austack-core (develop) Administrator@WIN-9PH4ISN44NM MINGW64 /e/zan/www/node/austack-core (develop)
E:\zan\www\node\austack-core\dist Error: listen EADDRINUSE 0.0.0.0:9001 npm ERR! Windows_NT 6.1.7601 npm ERR! Please include the following file with any support request: |
Sorry, I get time now to handle it. |
'.' ▒▒▒▒▒ڲ▒▒▒▒ⲿ▒▒▒Ҳ▒▒▒ǿ▒▒▒▒еij▒▒▒
▒▒▒▒▒▒▒▒▒ļ▒▒▒
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\nodejs\node.exe" "D:\nodejs\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v4.1.2
npm ERR! npm v2.14.4
npm ERR! code ELIFECYCLE
npm ERR! [email protected] postinstall:
./node_modules/gulp-protractor/node_modules/protractor/bin/webdriver-manager update
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script './node_modules/gulp-protractor/node_modules/protractor/bin/webdriver-manager update'.
npm ERR! This is most likely a problem with the austack package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! ./node_modules/gulp-protractor/node_modules/protractor/bin/webdriver-manager update
npm ERR! You can get their info via:
npm ERR! npm owner ls austack
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! E:\zan\www\node\austack-core\npm-debug.log
The text was updated successfully, but these errors were encountered: