feat!: migrate to Vite 6 environment API

[hi-ogawa]

• closes rewrite to Vite 6 environment api #378
• reference https://github.com/hi-ogawa/vite-environment-examples/tree/main/examples/react-server

todo

• global reactServer -> reactServerRunner
• plugin switch this.environment.name === "react-server"
• serverDepsConfigPlugin
• validateImportPlugin
• buildOrchestrationPlugin
• vitePluginServerAssets, serverAssetsPluginServer
• routeManifestPluginServer
• css
• hmr
• postcss (tailwind)
• rename environments['react-server'] to environments.rsc fix: update environment name for allowed characters vite-environment-examples#129
• fix import.meta.env.VITE_ENV_TEST reload
• refactor
  • use applyToEnvironment: (env) => Plugin[]
  • move to environments.client and environments.ssr config
  • unify plugins (use more this.environment.name switch)
  • use vite build --app instead of orchestrating during writeBundle
• test
  • chore(deps): vite 6 next-app-router-playground#11
• release examples

feedback? bug?

• "Re-optimizing dependencies because vite config has changed" shows up on every "vite dev"?
  • resolve.noExternal was unstable due to crawlFrameworkPkgs, but this array is not normalized by Vite's hashing
• unocss ssr build warning?
  • ah, this is same as Vite 5 and it's expected. https://github.com/hi-ogawa/vite-plugins/actions/runs/10608068778/job/29401566516#step:5:93
• applyToEnvironment is clumsy?

[hi-ogawa]

• feat!: migrate to Vite 6 environment API #634 👈 (View in Graphite)
• feat!: support Vite 6 #297 : 1 other dependent PR (#592 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[salomartin]

Any updates on this, given the Vite 6 release?

[hi-ogawa]

@salomartin Thanks for the interest! I would like to get back to this, but I have other priorities right now, so it might take some time 🙏