jeffbski / jeffbski/wait-on

How to use with long running SSR frameworks, EADDRINUSE due to terminal exiting after on first run

Open
#157 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
2k
Forks
87
PR merge metrics
No merged PRs in 30d

Description

when using wait on likes this

![image](https://github.com/jeffbski/wait-on/assets/216566/d5d9055d-c0c0-4ef6-b606-eeeea3281057)

it will exit terminal but leave the app running resulting on an error when run again

![image](https://github.com/jeffbski/wait-on/assets/216566/2478bcc2-ba52-4184-93aa-0219cc6619cd)

I have to manually kill ports
![image](https://github.com/jeffbski/wait-on/assets/216566/0cf6a535-8968-4b5a-a354-395ba4bf5444)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the long-running SSR usage described in the issue and observe what happens when the terminal exits after the first run. Investigate the wait-on CLI's process lifecycle and verify that a subsequent run does not encounter EADDRINUSE or require manually killing ports.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.