-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
events.js:182 throw er; // Unhandled 'error' event #1767
Comments
I am am having what seems to be the same issue. Any ideas about of what's going on here? DONE Compiled successfully in 317ms 11:09:48 PM
I Your site is running at http://localhost:8000
I Your graphql debugger is running at http://localhost:8000/___graphql
events.js:160
throw er; // Unhandled 'error' event
^
Error: watch /home/username/_Code/project-dir/node_modules/find-node-modules/test/b/c/d/e/f ENOSPC
at exports._errnoException (util.js:1020:11)
at FSWatcher.start (fs.js:1443:19)
at Object.fs.watch (fs.js:1470:11)
at createFsWatchInstance (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:37:15)
at setFsWatchListener (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:80:15)
at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:228:14)
at FSWatcher.NodeFsHandler._handleDir (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:407:19)
at FSWatcher.<anonymous> (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:455:19)
at FSWatcher.<anonymous> (/home/username/_Code/project-dir/node_modules/chokidar/lib/nodefs-handler.js:460:16) NOTE:
|
the old "reboot the system" fixed it... EDIT: I am having this issue again :/ |
Might want to check out jestjs/jest#3254 @Sotocodes |
I also got error with chokidar and this error code migrating from a hugo site with nested folders in |
For what it's worth, I ran |
I have The same error !! |
Closing older issues, please open new issues if you need more help! |
My 8080 post was taken, so I got this same error |
i also have the issue with the events.js:137 This happens when I try to create-react-app and also I am not able to run react app |
events.js:167 Error: spawn C:\Program Files\nodejs ENOENT |
Changing the port number worked for me |
In my MAC, I ran "killall node" and "yarn start" (or npm start) and everything is fine now. |
@juliancorrea thanks man. executing |
|
events.js:167 Error: EACCES: permission denied, open '/data/data/com.termux/files/home/hexoproject/source/_posts/科学上网软件ss系列.md' |
All you have to do is close all other open terminals. Also in my case I had working through Intellij, and when ever I closed the terminal, i had to make my way back to the folder with the js file. |
This fix for me:
Source: Node.JS Error: ENOSPC |
if you are on node project, kindly change the port number. if it was port Listen="3004", make it port listing ="3005" |
After closed the Intellij idea my problem solved. |
Check this ,solved mine https://stackoverflow.com/questions/43931986/how-to-upgrade-angular-cli-to-the-latest-version |
@kw3ku be right, in my case used port 80 i changed to 3000 it running normally now. |
Right!My project port number changed to 3200 just fine. Previously number 9080. |
|
Run |
Due to some reason in my system variables my path was not set. In case it doesn't work, try killing your port already under use. (Source) |
In my case, I resolved it by following steps
|
Thanks.And through which tutorial you install ReactJs?
…On Mon, Mar 30, 2020 at 9:58 AM Ashish Agrawat ***@***.***> wrote:
In my case, I resolved it by following steps
1. Delete node module files
2. Change in pakage.json
"react-scripts": "3.4.1" to "react-scripts": "1.1.1"
3. than use npm install
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZMHTEQZUDRLTUBHDVLRKARINANCNFSM4DWRE5IA>
.
|
@muqadas12 .... I followed react js official doc |
OK!.Thanks a lot
…On Mon, Mar 30, 2020 at 10:41 AM Ashish Agrawat ***@***.***> wrote:
@muqadas12 <https://github.com/muqadas12> .... I followed react js
official doc
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZPOKKYL5XZRY34CNVDRKAWJJANCNFSM4DWRE5IA>
.
|
it doesn't work .Giving same error again
…On Mon, Mar 30, 2020 at 9:58 AM Ashish Agrawat ***@***.***> wrote:
In my case, I resolved it by following steps
1. Delete node module files
2. Change in pakage.json
"react-scripts": "3.4.1" to "react-scripts": "1.1.1"
3. than use npm install
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZMHTEQZUDRLTUBHDVLRKARINANCNFSM4DWRE5IA>
.
|
I had an error like this and believe I caused it by moving the mySQL Server 8.0 folder outside of the MySQL folder into Program Files. (I originally did this because using mySQL in command line was annoying typing mySQL and then mySQL Server 8.0). |
npm install -g serve (si te sale error no importa) |
service docker restart ! |
npm install react-scripts --save |
nesse link abaixo tem uma solução que me ajudou https://peterthaleikis.com/posts/how-to-fix-throw-er-unhandled-error-event.html |
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p |
I have no idea what this does, but IT WORKED!!! Thanks |
Try to change port no : 3000 to 8080
** |
I did exactly this and it works now. Any idea why this might be happening? |
No I have no idea about this
…On Mon, Jun 29, 2020 at 6:06 PM Vaibhav Ahuja ***@***.***> wrote:
All you have to do is close all other open terminals.
Also in my case I had working through Intellij, and when ever I closed the
terminal, i had to make my way back to the folder with the js file.
I did exactly this and it works now. Any idea why this might be happening?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZKWTLW32LLACXCASU3RZCGVDANCNFSM4DWRE5IA>
.
|
I am facing this problem when i was using command: browser-sync start --server --directory --files "**/*" |
OK.Thanks
…On Mon, Jul 20, 2020 at 4:08 PM M-Hasnain ***@***.***> wrote:
I am facing this problem when i was using command browser-sync start
--server --directory --files "**/*"
This error is occurring, because we are not in working directory, i
changed the working directory, typed command again and it worked fine.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZLUXWVWXXA3R7DIQGLR4QQSPANCNFSM4DWRE5IA>
.
|
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p its work for me thanks |
events.js:292 please solve these error earliest |
Event.js:292 |
In my case the problem was due to path variable.i haven't set the path
after setting it I didn't receive this error
…On Mon, 24 Aug 2020, 8:05 PM Paridhinigam, ***@***.***> wrote:
Event.js:292
Throw er; // unhandled 'error' event
How to solve this error
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZJTM3KWZFQEPACIISTSCJ6THANCNFSM4DWRE5IA>
.
|
Thankyou so much.... can you help me ..how to set the path. |
Go to This pc
then properties
then Environment variable
and add the path of node js there
On Mon, Aug 24, 2020 at 6:58 PM Paridhinigam <[email protected]>
wrote:
… In my case the problem was due to path variable.i haven't set the path
after setting it I didn't receive this error
… <#m_2070613592314803608_>
On Mon, 24 Aug 2020, 8:05 PM Paridhinigam, *@*.***> wrote: Event.js:292
Throw er; // unhandled 'error' event How to solve this error — You are
receiving this because you were mentioned. Reply to this email directly,
view it on GitHub <#1767 (comment)
<#1767 (comment)>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AONDSZJTM3KWZFQEPACIISTSCJ6THANCNFSM4DWRE5IA
.
Thankyou so much.... can you help me ..how to set the path.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZN2BVYAHLNHJBV4U2TSCMLFXANCNFSM4DWRE5IA>
.
|
Thankyou |
it is due to the path issue of nodejs. You have to set path in
the environmental variable carefully
…On Mon, Sep 14, 2020 at 12:06 AM aashishkot ***@***.***> wrote:
Hi
I am facing an issue while running the yarn start and after 94% it gives
error :
[image: Snip20200914_1]
<https://user-images.githubusercontent.com/22097062/93026248-411d9480-f622-11ea-8d3b-63896583c7ec.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1767 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AONDSZNMJ7YBI7UMWTBPTADSFUJ3HANCNFSM4DWRE5IA>
.
|
After command, gatsby develop (npm run develop) I have got an error.
Please, help.
Your site is running at http://localhost:8000
I Your graphql debugger is running at http://localhost:8000/___graphql
events.js:182
throw er; // Unhandled 'error' event
^
Error: watch /data/home/user/Sasha/Gatsbyjs/node_modules/babel-polyfill/node_modules/core-js/library/fn/array ENOSPC
at exports._errnoException (util.js:1024:11)
at FSWatcher.start (fs.js:1382:19)
at Object.fs.watch (fs.js:1408:11)
at createFsWatchInstance (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:37:15)
at setFsWatchListener (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:80:15)
at FSWatcher.NodeFsHandler._watchWithNodeFs (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:228:14)
at FSWatcher.NodeFsHandler._handleDir (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:407:19)
at FSWatcher. (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:455:19)
at FSWatcher. (/data/home/user/Sasha/Gatsbyjs/node_modules/chokidar/lib/nodefs-handler.js:460:16)
at FSReqWrap.oncomplete (fs.js:153:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] develop:
gatsby develop
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /data/home/user/.npm/_logs/2017-08-11T06_20_35_175Z-debug.log
The text was updated successfully, but these errors were encountered: