events.js:160 throw er; // Unhandled 'error

2019-02-01 08:17发布

The project I worked on was built with gulp.

Recently I updated the node version to v6.3.1. Then something came wrong.

A task named 'html' throws an error. Here is the part of error code of it.

bogon:toClient work$ gulp html
(node:2519) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

[10:26:10] Using gulpfile ~/Project/TIME_Cancer_Treatment_Centers_of_America(CTCA)/toClient/gulpfile.js
[10:26:10] Starting 'html'...
(node:2519) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

events.js:160
      throw er; // Unhandled 'error' event
      ^
Error: CSS parse error scripts/vendor.js: Unexpected input
    1 |!function(t,e){"object"==typeof module&&"object"==typeof module.exports?module.exports=t.document?e(t,!0):function(t){if(!t.document)throw new Error("jQuery requires a window with a document");return e(t)}:e(t)}("undefined"!=typeof window?window:this,function(t,e){function i(t){var e="length"in t&&t.length,i=J.type(t);return"function"!==i&&!J.isWindow(t)&&(!(1!==t.nodeType||!e)||("array"===i||0===e||

And the code of task 'html':

var $ = require('gulp-load-plugins')();

gulp.task('html', function() {
  var assets = $.useref.assets({searchPath: ['.tmp']});

  return gulp.src('app/*.html')
    .pipe(assets)
    .pipe($.if('*.js', $.uglify()))
    .pipe($.if('*.css', $.csso()))
    .pipe(assets.restore())
    .pipe($.useref())
    .pipe($.if('*.html', $.minifyHtml({conditionals: true, loose: true})))
    .pipe(gulp.dest('dist'));
});

I googled a lot but I haven't found a proper answer suitable for me.

12条回答
趁早两清
2楼-- · 2019-02-01 08:48

Regarding the error at the following line:

events.js:160
      throw er; // Unhandled 'error' event

The issue for me was that I already had the port open on another local node app.

Stopping the other app resolved the issue.

查看更多
Juvenile、少年°
3楼-- · 2019-02-01 08:49

events.js:160

This is because

  1. The port using another node so you change the port of node from server.js

    2.or stop the other app use the same port .

查看更多
淡お忘
4楼-- · 2019-02-01 08:53

I was facing similar error on Ubuntu, while running a command npm start

Running sudo npm start solved my problem

I think this is because folder doesn't have write permission for Morgan logger.

查看更多
Rolldiameter
5楼-- · 2019-02-01 08:54

Lately, I changed the node version to v5.10.0 and everything just acted well.

查看更多
beautiful°
6楼-- · 2019-02-01 08:54

I was getting the same error while starting laravel-echo-server npm package. PFA image for reference. I think if you are getting error beacuse of any npm package this answer will be helpful to you.

enter image description here

How I found solution :

  • My domain was not properly configured. Check in the image, I'm trying to hit pid.contentcentral.co domain, which was disabled or not properly configured. Hence throws the error. Correction in the configuration and issue resolved.

Other Important points :

  • Error: listen EADDRNOTAVAIL error in Node.js

    When you see this line in error not the port but definitely your IP Address / Domain has got some trouble.

  • Error: listen EADDRINUSE

    When you see this line in error not your IP Address / Domain but definitely port has got some trouble may be already in use.

查看更多
闹够了就滚
7楼-- · 2019-02-01 08:55

Try to kill other gulp processes.

ps -ax | grep gulp
kill -9 <number>
查看更多
登录 后发表回答