wasp-lang/wasp

Improve how Wasp handles and reports unavailable ports

Open

#2427 opened on Dec 20, 2024

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Haskell (4,229 stars) (227 forks)batch import
dxgood first issueshouldfix

Description

Version: 0.15.2

Steps to reproduce:

  • Start a process (not Wasp) that listens on port 3001. For example: python -m http.server 3000
  • Execute wasp start.
  • Wasp will fail and tell you "Port 3001 is taken" (not 3000).

What happens:

  • The client sees port 3000 is taken and automatically falls back to 3001.
  • The server sees port 3001 is taken and crashes with the incorrect error.

It's a confusing experience because the client's message that says "Port 3000 is in use, trying another one..." is printed earlier and gets lost in the noise, while the server's message that says "Port 3001 is already in use" is the last (and possibly the only) thing the user sees.

@Martinsos Don't we already have an issue for this? I couldn't find it.

Contributor guide

Tech stack
nodejsreactjavascripttypescript
Domain
clideveloper experiencebackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Investigate the Wasp CLI source code, particularly in the command handler for 'wasp start', where port allocation and fallback logic is implemented. The error message for the server currently shows 'Port 3001 is taken' incorrectly. Look at the parts handling client and server port selection to understand the flow and identify where the bug occurs. Consider also the recent conversation in the issue for any hints.