feat(nuxt): allow configuring default <NuxtLink> options

[danielroe]

🔗 Linked issue

❓ 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 PR allows configuring NuxtLink defaults, such as trailing slash behaviour and default classes/prefetch behaviour. All of these are serialisable and initially can be set in experimental.defaults.nuxtLink but we will likely want to move to appConfig or app/ directory later on.

Example:

export default defineNuxtConfig({
  experimental: {
    defaults: {
      nuxtLink: {
        activeClass: 'nuxt-link-active',
        trailingSlash: 'append'
      }
    }
  }
})

📝 Checklist

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

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[danielroe]

Current dependencies on/for this PR:

• main
  • PR feat(nuxt): allow configuring default <NuxtLink> options #23724 👈
    • PR feat(nuxt): allow customising defaults for data composables #23725

This comment was auto-generated by Graphite.

[lihbr]

LGTM, I had concerns about default serialization behavior if users provided null/undefined/false to experimental.defaults.nuxtLink but defu + TypeScript should prevent that 👌

[manniL]

I had concerns about default serialization behavior

Came to my mind too but I also think that should be fine 👍