Development server keeps crashing

fadingbeat · July 20, 2023, 12:01pm

Hi,

I know this has probably been mentioned many times. The error I get is res.WriteHead is not a function. I used to get this error before when I would have localhost opened in more than one browser. I resolved that issue simply by running only one instance of the app. Now, every time I make a change to the code while the Netlify development server is running, the server crashes with for-mentioned error.

So, the site is not deployed, running it locally.

Here is the complete log I get:
https://justpaste.it/b9waj

I haven’t noticed server crashing while using the app, only when I make changes to the code. Any ideas?

It’s not really that big of an issue, but it gets annoying to have to run the server over and over again.

SamO · July 20, 2023, 4:15pm

What version of the CLI are you using?

fadingbeat · July 21, 2023, 7:15am

Version of the cli is 15.1.0

hrishikesh · July 23, 2023, 4:57pm

Please open an issue on CLI repo. Here’s one related: Browser session doesn’t recover after edge function failure · Issue #5676 · netlify/cli (github.com)

fadingbeat · August 2, 2023, 10:18am

Submitted issue on CLI repo:

github.com/netlify/cli

Netlify dev server crashes upon saving code changes

opened 10:17AM - 02 Aug 23 UTC

fadingbeat

type: bug

### Describe the bug If development server is running and I create a change in …the code, upon saving those changes the server crashes. It also crashes if I switch between Git branches. The instance of application is running in the browser constantly. There are a couple of scenarios I've noticed this happening. ### Steps to reproduce Scenarion 1: 1. Run `netlify dev` 2. App is started in the browser, everything works as expected 3. Change something in the code and save it 4. Dev server crashes with message `res.writeHead is not a function` Scenario 2: 1. Run `netlify dev ` 2. App is started in the browser, everything works as expected 3. Commit changes 4. Switch between branches 5. Dev server crashes with message `res.writeHead is not a function` Scenario 3: 1. Netlify server running 2. Change CSS styles 3. Server crashes 4. Run `netlify dev` 5. Reload browser 6. Server crashes ``` TypeError: res.writeHead is not a function at ProxyServer.<anonymous> (file:///C:/Development/color-healing/node_modules/netlify-cli/src/utils/proxy.mjs:362:9) at ProxyServer.emit (C:\Development\color-healing\node_modules\netlify-cli\node_modules\eventemitter3\index.js:204:33) at Socket.onOutgoingError (C:\Development\color-healing\node_modules\netlify-cli\node_modules\http-proxy\lib\http-proxy\passes\ws-incoming.js:157:16) at Socket.emit (node:events:524:35) at Socket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:151:8) at emitErrorCloseNT (node:internal/streams/destroy:116:3) at processTicksAndRejections (node:internal/process/task_queues:82:21) Node.js v19.6.0 fatal error: all goroutines are asleep - deadlock! ``` ### Configuration ``` [build] command = "npm run build" functions = "functions" publish = "dist/color-healing" [functions] node_bundler = "esbuild" [dev] autoLaunch = false [[redirects]] from = "/*" to = "/" status = 200 ``` ### Environment ``` System: OS: Windows 10 10.0.19045 CPU: (4) x64 AMD A10-7300 Radeon R6, 10 Compute Cores 4C+6G Memory: 4.16 GB / 9.95 GB Binaries: Node: 19.6.0 - C:\Program Files\nodejs\node.EXE npm: 9.4.0 - C:\Program Files\nodejs\npm.CMD npmPackages: netlify-cli: 15.1.0 => 15.1.0 ```

fadingbeat · August 6, 2023, 2:03pm

I am using VS Code, and so I thought maybe the issue is related to the editor.
Tried running development server in separate CMD window, issue persists.
I let it re-compile without switching between windows or opening browser, it would still crash.
Sometimes it compiles, but then it crashes immediately afterwards.
I run it again, it compiles and again it crashes.

Basically, it keeps crashing all the time and I think it has something to do with client side, because if I only load the Netlify function in the browser, it doesn’t crash upon changes.

hrishikesh · August 6, 2023, 3:11pm

Hey @fadingbeat,

I have pinged the devs internally. However, I’m not sure if/when they will take a look at this issue. CLI-issues are not handled by Support, so I’ll leave it for the devs to decide when they wish to take this up and investigate. Any follow-ups would mostly happen in that issue.