fix(schema): disallow setting vite server properties

[manniL]

🔗 Linked issue

nuxt/nuxt#14828

❓ Type of change

• 👌 Enhancement (improving an existing functionality like performance)

📚 Description

Disallows setting the port via vite.server.port in the nuxt.config.ts.
@pi0 Any other options we should disallow? Or vite.server in general?

📝 Checklist

• I have linked an issue or discussion.

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	7229be7
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/63187fa33ffb9d0008f6a3e1

[pi0]

@pi0 Any other options we should disallow? Or vite.server in general?

I think makes sense to server vite.server to never too 👍🏼 (quickly) checking code we are not using it at all.

[nndnha]

I want to set Vite build sourcemap option to "hidden" mode so my nuxtConfig was:

vite: {
    build: {
      sourcemap: "hidden",
    },
  },

this PR breaks my config then how can I passed some configurations to Vite with this new change?

[tobiasdiez]

Setting server no never now leads to ts errors for hmr configs that are sometimes necessary (e.g. for gitpod):

vite: {
    server: {
      hmr: ...
    }
}

But hmr is not exposed by the top-level server config. What is the correct config with rc.10?

[pi0]

@tobiasdiez Can you please open a PR to limit never to only port/host options? Configuring vite.server.hmr is valid.

[manniL]

@tobiasdiez Can you please open a PR to limit never to only port/host options? Configuring vite.server.hmr is valid.

Will fix this ☺️