use same development server port for production
Open
Nobody has claimed this yet.
discussion
enhancement
v3
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
Right now when nitro is built using vite build, the output completely ignores the server.port configuration inside the vite config file. I think it would much more nice and intuitive to default to use the vite config's server.port rather than having a separate port configuration.
Additional information
- Would you be willing to help implement this feature?
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
Start by tracing how vite build handles the Vite config's server.port and where Nitro's separate production port is configured. Confirm the intended configuration path, then verify that the built production server uses the Vite port when no separate port is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vite
- Domain
- backend, build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100