vercel-labs / vercel-labs/dev3000
Support custom hostname for portless / .localhost URL compatibility
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 99
- Avg merge
- 20m
- Merged PRs (30d)
- 1
Description
d3k hardcodes localhost when constructing the browser URL (http://localhost:{port}). This makes it incompatible with tools like vercel-labs/portless that route via hostname (e.g. http://myapp.localhost:1355).
Running d3k --command "portless myapp next dev" partially works. d3k picks up the random port from Next.js stdout and connects directly, bypassing the portless proxy. But this loses the named URL benefits (stable cookies, no port conflicts, readable URLs).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the TypeScript codebase for the browser URL construction that hardcodes http://localhost:{port}; the issue does not name a file or test. Trace how the d3k --command invocation and Next.js stdout port are handled, then verify that a custom hostname such as myapp.localhost is preserved so portless routing is used instead of connecting directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100