feat(schema,vite): allow $client and $server vite env overrides

[danielroe]

🔗 Linked issue

#13499 (comment)

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This allows configuring client/server configuration for vite directly in the Nuxt config, without needing to do so in a hook. This is pure convenience, but avoids issues where setting a vite configuration for the client ends up having negative implications for the server configuration, as in the linked issue above.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[pi0]

This is a nice idea for env (client/server) specific configuration. However, I'm a little bit concerned about making it "vite" specific. It could be extended to other bundlers (webpack) but also possibly for edge cases such as app config which is client/server specific. I think we can move forward with this and always alias only to mention about possibility of a (more generic) feature.

[danielroe]

Yes, I think we should support webpack out of the box (will implement in a parallel PR) 👍

[danielroe]

@pi0 Any changes you would suggest? I don't think there's anything blocking us from refactoring to a native c12 feature if we end up building it.