Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Ctrl+c not killing running dev; leaving ports open

See original GitHub issue

Describe the bug

In the default next.js template from superplate, after I run the server with pnpm run dev and use ctrl+c to stop it from running, upon re-running dev later, I see:

warn - Port 3000 is in use, trying 3001 instead.

This is because the first dev run was on 3000 and the node.exe process is still running. This problem never resolves.

Steps To Reproduce

Included

Expected behavior

Kills node process. Run on same port as before without having to go +1

Screenshot

No response

Desktop

node v18.12.1 LTS Windows 10

Mobile

No response

Additional Context

No response

Issue Analytics

State:
Created 9 months ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

yasnbouzcommented, Dec 22, 2022

Hey @omeraplak, I’ve patched @pankod/refine-cli and it works well with windowsHide:false also, I notice the terminal has no color, it works well with FORCE_COLOR=1 pnpm dev Could you make the env variable FORCE_COLOR enable by default These is execa options i’ve used: { stdio:"pipe",windowsHide:false,env:{FORCE_COLOR:1,...process.env} }

1reaction

alicanerdurmazcommented, Dec 9, 2022

Hi @drewbitt, Please, can you share package.json with us ?