feat(Link): automatically use localePath from @nuxtjs/i18n

[benjamincanac]

🔗 Linked issue

Resolves #5536, resolves #5359, resolves #5637

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

📝 Checklist

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

[benjamincanac]

@BobbieGoede I'd love your feedback on this, would this work?

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@5537

commit: c8a7002

[benjamincanac]

@BobbieGoede I have another question, what will happen if users have already passed localePath or localeRoute to the to prop? I don't want to break existing apps 😬

[BobbieGoede]

@BobbieGoede I have another question, what will happen if users have already passed localePath or localeRoute to the to prop? I don't want to break existing apps 😬

Passing localized paths/routes to localePath and localeRoute should work, but will still localize it to the current language since no locale parameter is passed, so this is breaking for users passing localized paths pointing to other languages.

You might want to add a prop to the component so users can both opt-in to localization and/or specify the language (something like locale: true | string). You could also add a config option to invert it so that it's opt-out instead (like this draft for example nuxt-modules/i18n#3530).