Have to restart local devserver manually when we change code

Get Help and Help Others
1

Hi, our local dev server is broken on latest stable v7.7.4.
This is happening for all devs.

api | 09:37:05 🌲 Server listening at http://localhost:8911
api | Took 2836 ms
api | API server listening at http://localhost:8911/
api | GraphQL endpoint at http://localhost:8911/graphql
api | [change] /src/services/tasks/tasks.ts
api | Building...
api | Took 4052 ms
api | Starting inspector on 127.0.0.1:18911 failed: address already in use
api | Starting API Server...
api | Importing Server Functions... 
api | [hive] Missing token, disabling.
api | /graphql 2609 ms
api | ...Done importing in 2610 ms
api | rw-server api
api | 
api | Start a server for serving the api side
api | 
api | Options:
api |   -p, --port                                The port to listen at       [number]
api |       --host                                The host to listen at. Note that you
api |                                             most likely want this to be
api |                                             '0.0.0.0' in production     [string]
api |       --apiRootPath, --api-root-path,       Root path where your api functions
api |       --rootPath, --root-path               are served   [string] [default: "/"]
api |   -h, --help                                Show help                  [boolean]
api |   -v, --version                             Show version number        [boolean]
api | 
api | Error: listen EADDRINUSE: address already in use :::8911
api |     at Server.setupListenHandle [as _listen2] (node:net:1898:16)
api |     at listenInCluster (node:net:1946:12)
api |     at doListen (node:net:2116:7)
api |     at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
api |   code: 'EADDRINUSE',
api |   errno: -48,
api |   syscall: 'listen',
api |   address: '::',
api |   port: 8911
api | }
^Cweb | yarn cross-env NODE_ENV=development rw-vite-dev  exited with code 0
gen | yarn rw-gen-watch exited with code 130
2

Hi @jonoc330,

We have had this issue too and discussed it in the v7.0.0 Upgrade guide and @callingmedic911 made a fix for the issue here.

As far as I can tell from the GitHub PR linked in the post above and the early release candidate for v8.0.0, this fix, unfortunately, won’t be live until we get v8 :pensive:

I have found that the best way to avoid the issue is to disable auto-save in your editor because it will trigger multiple rebuilds if you make many consecutive file changes in the backend. Also, if you switch between branches where there are multiple file changes in the backend, then you’re better off restarting the dev server completely.

3

Hey @lars I’ve upgrade to v8 and I’m still getting this issue

4

Are you using Windows/Linux/MacOS? I have moved from Windows to Linux and have rarely experienced the issue since then. I wasn’t able to reproduce the error on our branch that upgrades to v8

5

On MacOS