fix(nuxt): fix router redirection on aliased page

[huang-julien]

resolvenuxt/nuxt#13970

🔗 Linked issue

nuxt/nuxt#13970

❓ 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

Using the force option on router replace make vue router use the name key in priority to match and retrieve the router location object resulting in a redirection such as the one described in the linked issue. We should just remove the name key from the object passed to router.replace when using force: true

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt3-docs canceled.

Name	Link
🔨 Latest commit	b5d3859
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt3-docs/deploys/62823e10bebb560009738ee0

[huang-julien]

@danielroe i just saw some warning in the CI that did not showed up in local, converting this to draft to confirm that there are not any side-effect

[huang-julien]

nvm, it seems that it just disapeared when it re-ran after accepting your suggestion 😄 . However if i remember well, vue-router does not handle very well routes alias with params

[pi0]

LGTM! I've noticed same issue on a previous investigation on redirect issues.