Navigation in the `UError` component does not work outside of Nuxt.

[agroebe]

Environment

• Operating System: Windows_NT
• Node Version: v24.11.0
• Nuxt Version: 4.2.1
• CLI Version: 3.30.0
• Nitro Version: 2.12.9
• Package Manager: pnpm@10.21.0
• Builder: -
• User Config: -
• Runtime Modules: -
• Build Modules: -

Is this bug related to Nuxt or Vue?

Vue

Package

v4.x

Version

v4.2.1

Reproduction

https://codesandbox.io/p/devbox/delicate-meadow-xppn8k

Description

The ability to "clear" the error in the UError component, thereby navigating to the redirect prop, does not work outside of Nuxt.

In Vue and Inertia, the clearErrors function is stubbed to do nothing at all. Is there any reason that those runtimes can't interact with their respective routers?

Far less relevant or consequential, it also occurred to me that the naming clearErrors only really applies to Nuxt. This is not a concept that exists in standard Vue or Intertia routers and thus it might make sense to rename that to something like handleRedirect or what not. But I'm not sure if that's a requirement of how the import stubbing is set up.

Additional context

No response

Logs

[benjamincanac]

This component was initially built for Nuxt, we made it compatible for Vue by stubbing the clearError function.

You can use the clear prop to configure the button with an onClick field for example to navigate where you want.

[agroebe]

This component was initially built for Nuxt, we made it compatible for Vue by stubbing the clearError function.

You can use the clear prop to configure the button with an onClick field for example to navigate where you want.

Makes perfect sense. Good to know there's a workaround, thank you!

IMO, I still think it is undesirable to render a button that does nothing by default. The redirect prop is also entirely obsolete outside of Nuxt.