We are pushing this issue out because it appears to be more complex than originally thought. A few discoveries:

• Vue 3 doesn't seem to catch errors in data like Vue 2 did. Internal data handling is missing error handling which doesn't let us just carry on like Vue2 did.
• vueApp.config.errorHandler is only configured for dev environment. This results in a blank page in production. We should add some error handling for non-dev setup.
• Adding ErrorBound doesn't seem to catch the error, but it can be worked around by using try-catch inside data.
• If you try to go to a page that throws error in data, it might cause a Vue error. This gets app in a weird state. We should come up with a repro and submit a bug report to Vue. Refreshing the page redirects the page to fail-whale like it should.

"[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/core 
  at <Index class="outlet" onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > 
  at <RouterView key="/c/_/manager/cloudCredential" class="outlet" > 
  at <Default onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< Proxy(Object) {_fetchDelay: 200, $fetch: ƒ, updatePageActions: ƒ, setCustomColor: ƒ, removeCustomColor: ƒ, …} > > 
  at <RouterView key=1 > 
  at <App>"

This can be reproduced by throwing an error inside data in 'shell/pages/c/_cluster/manager/cloudCredential/index.vue'

Some suggestions: #12198