![[SOLVED] events.js:160 throw er; // Unhandled 'error' event 1](https://cdn.piotrkrzyzek.com/eventsjs-160-throw-er2.png)
In a recent Laravel project I came across this rather annoying error:
|
1 |
events.js:160 throw er; // Unhandled 'error' event |
Though I didn't save the text of the whole error, here's a screenshot of the ending part of the error log:
![[SOLVED] events.js:160 throw er; // Unhandled 'error' event 2](https://cdn.piotrkrzyzek.com/Screen-Shot-2017-02-14-at-4.png)
The solution:
It's really easy. All this really means so far is that there's a code mis-match probably between what you're Node.js & NPM versions are and what the code you're using requires and uses. First and foremost: upgrade your Node.js (and thus NPM) install to the latest version.
After that, clear out the node_modules folder, clear the node cache and reinstall the node modules. You can do the following commands:
|
1 2 3 |
rm -rf node_modules npm cache clean npm install |
![[SOLVED] events.js:160 throw er; // Unhandled 'error' event 3](https://cdn.piotrkrzyzek.com/Screen-Shot-2017-02-14-at-4.15.29-PM.png){kind=small}
At which point it'll start re-installing all the modules:
![[SOLVED] events.js:160 throw er; // Unhandled 'error' event 4](https://cdn.piotrkrzyzek.com/Screen-Shot-2017-02-14-at-4.21.23-PM.png)
[…] [SOLVED] events.js:160 throw er; // Unhandled 'error' event – In a recent Laravel project I came across this rather annoying error Though I didn't save the text of the whole error, here's a screenshot of the ending part of the error log […]