Navigation breaks upon unrelated error

[Neevalt]

Hello there,

We are migrating an app from webpack to vite, and while doing so I found a strange behavior. It seems that with our new version, an error (like component script execution) will freeze the navigation. You can find a reproduction here
https://stackblitz.com/edit/vitejs-vite-cxexlrbk?file=src%2FApp.vue,src%2Fmain.ts,src%2Frouter.ts,package.json,src%2FHome.vue,src%2FSync.vue&terminal=dev

Home page is fine, Sync page has a div with a class that tries to access an item on undefined. Once arriving on the sync page and the error triggers, the Home page (with "Home view" message) is can not be accessed anymore (though the url will change).

Is this intended ? For our project it can be inconvenient as multiple teams work on the same codebase and sometimes an error (that doesn't necessarily breaks the page in terms of business, just a component won't display for instance) and that error can't be fixed right away, but not being able to do navigation anymore is a bit inconvenient.

I don't know if it's worth mentionning, but removing the key in the RouterView changes the behavior a bit, the error preventing navigation will not re-appear upon trying to navigate again.

Thanks in advance

[posva]

This wasn't intended but was part of the new behavior of RouterView with Vue 3. In practice, you are not expected to deploy applications with these kind of errors as they mean the page will always break when loaded. You can catch them with an error handler:

const app = createApp(App)
app.config.errorHandler = (e) => {
  console.log('OH NO', e)
}

[Neevalt]

Hi, thanks for answering.
I agree, we shouldn't ever be in this case ideally, but sometimes there's a mess up in the chain somewhere (usually the back-end) on which we don't have much room beside "guys can you fix this please ?".
It's not really a problem for our client, you can see in the stackblitz that building to production logs the error but doesn't break navigation, it's more of an inconvenience during dev.

That being said, configuring the errorHandler seems to un-break it, thank you for that. Do you foresee any unwanted side effect of doing that that we would have worse impact that inconvenient dev-exp ?

[posva]

No, it should be fine