NuxtLinkLocale missing default slots props

[userquin]

Environment

Nuxt project info:                                                                                                                                     13:42:46

------------------------------
- Operating System: Windows_NT
- Node Version:     v20.10.0
- Nuxt Version:     3.10.3
- CLI Version:      3.10.1
- Nitro Version:    2.8.1
- Package Manager:  [email protected]
- Builder:          -
- User Config:      typescript, modules, vue, macros, devtools, features, experimental, css, alias, imports, vite, postcss, appConfig, runtimeConfig, routeRules,
 nitro, sourcemap, hooks, app, security, colorMode, i18n, pwa, staleDep, unlazy
- Runtime Modules:  @vueuse/[email protected], @unocss/[email protected], @pinia/[email protected], @vue-macros/[email protected], @nuxtjs/[email protected], @nuxtjs/[email protected], @unlazy/nu
[email protected], @nuxt/test-utils/[email protected], ~/modules/emoji-mart-translation, ~/modules/purge-comments, ~/modules/build-env, ~/modules/tauri/index, ~/modules/pwa/
index, stale-dep/nuxt
- Build Modules:    -
------------------------------

Reproduction

NuxtLinkLocale rendering default slot without props: https://github.com/nuxt-modules/i18n/blob/main/src/runtime/components/NuxtLinkLocale.ts#L81

NuxtLink rendering default slot with props: https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/app/components/nuxt-link.ts#L362

Example in elk.zone repo: https://github.com/elk-zone/elk/blob/95e466146d3b92ec212b725b0379a04a2eeeb6de/components/account/AccountPostsFollowers.vue#L14-L28

Describe the bug

When using NuxtLinkLocale with default slot props we get errors about missing props (trying to use NuxtLinkLocale in elk.zone):

Additional context

No response

Logs

[github-actions[bot]]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 Reproduction starter (v8 and higher) 👉 Reproduction starter (edge)

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example