feat: preview config

[patak-dev]

Description

Continuation from #5407

We create a new userConfig.preview: { port: 5000, ... } config option and a resolvedConfig.preview that has the resolved info for the preview server. There is a new CommonServerOptions interface that is shared and a new PreviewServerOptions. The preview server defaults to the options in dev server for host, strictPort, https, cors, proxy, and open (I'm not sure about this last one), but not for port. This would allow the user to define the preview port in vite.config.js instead of in the package.json script. It is more clear to see in the ResolvedConfig the resolved HTTP server options for the dev server and the preview server separately.

This PR deprecates printHttpServerUrls because it doesn't work now that config.server and config.preview are separate in ResolvedConfig. It still works fine for printing the URLs from the server, that is what the ecosystem could be using this function for (as the experimental preview API was just exposed). Users of createServer and preview should use server.printUrls(). Maybe we should expose. The only place I see it being used is in Vitedge here https://github.com/frandiox/vitedge/blob/d64b6bc46988bf9df6896a32e499453d52476fbf/src/build/preview.js#L76, but this would continue to work.

src/node/server/http.ts has been moved to src/node/http.ts as it is shared between the dev server and the preview server

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

[Shinigami92]

@patak-js Is this really a feat? Or is it a refactor?

[patak-dev]

It is a feat, it adds new config options. You can now specify the preview server port in vite.config.js

Add a test that uses the new preview property

[Shinigami92]

Could you also please provide an example how such a new vite config would look like? 🙂

We should also think about that proxy and cors should be moved out from common to only dev config 🤔 But this should be done in another PR

[patak-dev]

Added docs for preview. @Shinigami92 I checked how we could test the preview server and it isn't clear. We are currently using a custom static server during build test, maybe a good way to test it would be to replace it with the preview server. But this needs to be analyzed separately from this PR

vite/scripts/jestPerTestSetup.ts

Line 158 in 09e2a5f

function startStaticServer(): Promise<string> {

I'll merge this without extra tests at this point, test coverage remains the same as before this PR (we are only testing that the preview server starts correctly in the cli playground).

[Shinigami92]

@patak-js What I would like to get tested is the preview property, so it get's read out from the config
Maybe it's possible with a simple unit test? Or maybe mocked?