use same development server port for production

[onlywei]

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?

[kricsleo]

The server.port config in Vite seems to only work with vite dev. What do you mean by "using vite build"? 🤔 (Maybe I don't get it)

[onlywei]

The server.port config in Vite seems to only work with vite dev. What do you mean by "using vite build"? 🤔 (Maybe I don't get it)

I want it to also work when I do:

vite build
node .output/server/index.mjs

[pi0]

It would be a nice idea, but we have to think about the consequences. For example, many self-hosted deployments assumethe default port is 3000 but with this, a change to dev server config might unwillingly break prod (also as @kricsleo mentioned, vite server config is meant for dev/preview rather than prod)

Regardless even if we want to implement it, we need a sub-task to support build-time server options for node (for example port). This will at least allow setting two ports between dev and prod to be same.

[onlywei]

Environment variables should always override any other configs for port.

This is feature request is mainly to test the production build of the server locally before actually sending it to production.

All of my local servers operate together with another locally running reverse proxy server that expects each other app to have a consistent local port.

[onlywei]

Regarding the build time server options, the way I've done it in @fastify/vite is to write the relevant vite configurations into a json file in the output folder.

I can try to do that again for this project if you like.