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

Question

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.

Possible duplicate of [Node.js – events js 72 throw er unhandled 'error' event](http://stackoverflow.com/questions/22960703/node-js-events-js-72-throw-er-unhandled-error-event) — Jonny Henly, Aug 09 '16 at 02:43
https://stackoverflow.com/questions/51630227/events-js167-throw-er-unhandled-error-event — Dinesh Naik, Mar 06 '20 at 05:31

lasec0203 · Accepted Answer · 2018-07-05T17:54:10.883

65

removing the node_modules folder, clearing npm cached files, and doing a fresh install, resolves this issue.

rm -rf node_modules && npm cache clean --force && npm install

source: https://github.com/ember-cli/ember-cli/issues/3087#issuecomment-71327402

edited Jul 05 '18 at 17:54

answered Oct 05 '16 at 11:03

lasec0203

2,422
1
21
36

For me it requires to be always cleared after I restart my computer. Is there any way to avoid this issue? – Bruno Francisco Feb 11 '20 at 18:01

score 16 · Answer 2 · answered Sep 08 '17 at 05:06

16

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.

answered Sep 08 '17 at 05:06

QuietCoder

161
1
4

6

This issue was a huge headache and this answer came through, cheers! – Ryan Cocuzzo Apr 07 '18 at 20:02

score 6 · Answer 3 · answered Jun 28 '18 at 13:36

6

I was facing similar error while running my create-react-app on Ubuntu, while running a command npm start

It gets solved when I run sudo npm start

I think a problem might be with application not having enough permissions.

answered Jun 28 '18 at 13:36

Anand Kapdi

491
5
4

In my case, that happened after renaming the original folder create by the `create-app` cmd. Something to keep in mind. – Btc Sources Feb 04 '20 at 09:54

score 2 · Answer 4 · answered Aug 11 '16 at 02:03

2

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

answered Aug 11 '16 at 02:03

Heath Yang

471
1
4
10

score 2 · Answer 5 · answered Jan 26 '18 at 12:05

2

Try to kill other gulp processes.

ps -ax | grep gulp
kill -9 <number>

answered Jan 26 '18 at 12:05

Artemiy Zajcev

21
1

score 1 · Answer 6 · answered Apr 25 '17 at 13:22

I had similar problem with events.js.

[19:59:06] Starting 'jekyll-async'...

events.js:72
    throw er; // Unhandled 'error' event
          ^
Error: spawn ENOENT
    at errnoException (child_process.js:1011:11)
    at Process.ChildProcess._handle.onexit (child_process.js:802:34)

In my case problem occurred because I forgot to install gems from my Gemfile (after complete system reinstall).

So, cure for me was:

gem install jekyll

score 1 · Answer 7 · edited Aug 10 '17 at 09:11

1

In my case the port already in use..

# netstat -nltp

Check is there any thing running with port which are trying to start with..if yes change port and try.

Some cases IP address also may wrong if using static IP

edited Aug 10 '17 at 09:11

veganaiZe

539
5
13

answered Aug 08 '17 at 08:53

BEJGAM SHIVA PRASAD

2,181
1
18
27

score 1 · Answer 8 · answered Feb 23 '18 at 06:06

1

events.js:160

This is because

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 .

answered Feb 23 '18 at 06:06

hazan kazim

938
9
11

score 1 · Answer 9 · edited Jun 20 '20 at 09:12

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.

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.

Please add some code so other users can test what you're describing. Thanks! — Ignacio Ara, May 07 '18 at 07:43

score 1 · Answer 10 · answered Sep 20 '18 at 11:35

1

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.

answered Sep 20 '18 at 11:35

umer sayyed

56
2

score 0 · Answer 11 · answered Feb 06 '19 at 09:52

0

Solution: $event => can be used only .ts files.

 $scope.openFromCalendar = ($event) => {
        $event.preventDefault();
        $event.stopPropagation();

        $scope.fromCalendarOpened = true;
        $scope.ToCalendarOpened = false;
    };

If you are using .js files use it like

$scope.openFromCalendar = function ($event) {
                $event.preventDefault();
                $event.stopPropagation();
                $scope.fromCalendarOpened = true;
                $scope.ToCalendarOpened = false;
            };

answered Feb 06 '19 at 09:52

Mahesh A Kulkarni

1

1

This does not provide an answer to the question. You can [search for similar questions](https://stackoverflow.com/search), or refer to the related and linked questions on the right-hand side of the page to find an answer. If you have a related but different question, [ask a new question](https://stackoverflow.com/questions/ask), and include a link to this one to help provide context. See: [Ask questions, get answers, no distractions](https://stackoverflow.com/tour) – Stefan Becker Feb 06 '19 at 09:59

score 0 · Answer 12 · answered Mar 15 '20 at 18:37

0

Try running following command and after that perform your action, you want to perform

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

I hope it will work.

answered Mar 15 '20 at 18:37

Shahrukh Anwar

2,544
1
24
24

score 0 · Answer 13 · answered Jul 19 '20 at 02:04

0

set env var windows/system32
it will work for windows

answered Jul 19 '20 at 02:04

Mohammed Shabeer

11
2

Please provide solution with all steps if necessary. – Haseeb Mir Jul 19 '20 at 03:39

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

13 Answers13

Linked