Fsevents popup

Wappler Version : 3.7.4
Operating System : MacOS
Server Model: Node.js
Database Type: n/a
Hosting Type: n/a

===

New node project, after about 5/10 minutes I get this popup. I cancel it down and it re-appears again after a few minutes. Would using the terminal cause this?

Also receiving a local warning:

App listening at http://localhost:3000
[nodemon] 2.0.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): app/**/* lib/**/* views/**/* extensions tmp/**/restart.txt
[nodemon] watching extensions: ejs,js,json
[nodemon] starting `node ./index.js`
events.js:288
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3000
    at Server.setupListenHandle [as _listen2] (net.js:1309:16)
    at listenInCluster (net.js:1357:12)
    at Server.listen (net.js:1445:7)
    at Object.start (/Volumes/GoogleDrive/My Drive/1 WEB/Websites/maxgb/tailwind/lib/server.js:67:16)
    at Object.<anonymous> (/Volumes/GoogleDrive/My Drive/1 WEB/Websites/maxgb/tailwind/index.js:3:8)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32)
    at Function.Module._load (internal/modules/cjs/loader.js:901:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
Emitted 'error' event on Server instance at:
    at emitErrorNT (net.js:1336:8)
    at processTicksAndRejections (internal/process/task_queues.js:84:21) {
  code: 'EADDRINUSE',
  errno: 'EADDRINUSE',
  syscall: 'listen',
  address: '::',
  port: 3000
}
[nodemon] app crashed - waiting for file changes before starting...
rs

The first error happens if some of the node modules is using the native fsevents module that hasn’t been signed.

You can run:

npm list fsevents

To see which one.
Also if it is needed you can just go to your Mac security settings and accept the usage of fsevents - even if not signed.

Second errors is because the services are already running, try restarting Wappler fully.

1 Like

Fixed in Wappler 5.4.1

This topic was automatically closed after 24 hours. New replies are no longer allowed.