feat(nuxt): enable preloading object-syntax routes

[Mini-ghost]

🔗 Linked issue

• preloadRouteComponents allows passing values of type RouteLocationRaw #18845

❓ 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 like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

After this PR, the path parsed by the following code all will be /home. As a result, the preload function will not retry and will instead return early.

<!-- Passing a string -->
<NuxtLink to="/home"> Home </NuxtLink>

<!-- Passing a string with query string -->
<!-- `router.resolve('/home?year=2023').path` is `/home` -->
<NuxtLink to="/home?year=2023"> Home </NuxtLink>

<!-- Passing a object -->
<!-- `router.resolve({ name: 'home', query: { year: '2023' } }).path` is `/home` -->
<NuxtLink :to="{ name: 'home', query: { year: '2023' } }"> Home </NuxtLink>

In addition, when users use preloadRouteComponents, they are not limited to type string.

const route: RouteLocationRaw = {
  name: 'dashboard'
}

preloadRouteComponents(dashboard)
const submit = async () => {
  const results = await $fetch('/api/authentication')
  if (results.token) {
    await navigateTo(dashboard)
  }
}

📝 Checklist

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

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[danielroe]

Would you update this following the merge of your other PR? 🙏

[Mini-ghost]

Thank you for bringing this to my attention. I resolved the conflict caused by #19144.

[Mini-ghost]

I'm unsure which option is better between using name or path for dynamic route, Even though they resolve to the same page components, their paths may still differ. While name may not have this issue, it is possible for it to be undefined or null.

Does the name of the route always exist in Nuxt? If so, would it be better to use it?

Overall, this issue is not significant because although dynamic routing repeats preloading, it doesn't require sending additional network requests.

[danielroe]

name does not always exist, so I think better to use path.