fix(schema): add vueCompilerOptions property to TSConfig in defineNuxtConfig

[Evobaso-J]

🔗 Linked issue

#25874

❓ 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

Resolves #25874

VueCompilerOptions type added to the defineNuxtConfig schema

📝 Checklist

• I have linked an issue or discussion.
• I have added tests (if possible).
• I have updated the documentation accordingly.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[Evobaso-J]

@manniL Hi there!
This one is ready for code review. However, I'm not sure whether documentation on the VueCompilerOptions is needed or if a type addition, in general, is self-explanatory 🤔

By the way, I must say I couldn't find any reference to these options anywhere but on Volar's changelog, so having those documented somewhere could be nice!

Please let me know what you think ✌️
TY

[danielroe]

If the user doesn't have this dependency installed, this (and mention above in schema) will be typed as any. We could use something like this type:

type IsAny<T> = 0 extends 1 & T ? true : false

to conditionally augment tsConfig only when VueCompilerOptions is not any...

[Evobaso-J]

@danielroe changes made!
I've been pondering about it for some days now but I still don't quite understand one thing: how can the user not have the dependency installed if they're installing nuxt? 🤔
Also, why don't we need to make the same check for other dependencies as well?

[danielroe]

The user will only have this dependency installed if they add vue-tsc. Nuxt doesn't ship with vue-tsc by default.

[Evobaso-J]

Oh, I see! Thank you 😄

[danielroe]

Thank you ❤️