Skip to content

fix(startup): show correct Vite client URL in dev mode#101

Merged
justinchoo93 merged 1 commit intomainfrom
justin/improve-startup-logs
Feb 27, 2026
Merged

fix(startup): show correct Vite client URL in dev mode#101
justinchoo93 merged 1 commit intomainfrom
justin/improve-startup-logs

Conversation

@justinchoo93
Copy link
Copy Markdown
Collaborator

Summary

  • resolveVisitPort checked NODE_ENV === 'development' but dev scripts never set NODE_ENV, so the startup URL always pointed to the Express port (3001) instead of the Vite client port (5173)
  • Aligned with the rest of the codebase by checking !== 'production'
  • Added a dev mode hint line clarifying which port is the Vite client vs the Express server

Test plan

  • Updated startup-url.test.ts with corrected expectations for unset/test NODE_ENV
  • Added test for VITE_PORT respect when NODE_ENV is unset
  • Server test suite passes (113/113, 2 pre-existing failures in unrelated Windows path tests)

🤖 Generated with Claude Code

resolveVisitPort checked NODE_ENV === 'development' but dev scripts
never set NODE_ENV, so the startup URL always showed the Express port
(3001) instead of the Vite port (5173). Align with the rest of the
codebase by checking !== 'production'. Also add a dev mode hint line
clarifying which port is the client vs the server.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@justinchoo93 justinchoo93 merged commit 1959a7a into main Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UI stuck on Reconnecting after npm run dev - no auth URL printed at startup

1 participant