Unexpected Application Error!

Failed to fetch

TypeError: Failed to fetch
    at queryFn (http://localhost:4173/assets/index-Cn4t-bIz.js:189:384955)
    at Object.d [as fn] (http://localhost:4173/assets/index-Cn4t-bIz.js:189:395851)
    at G (http://localhost:4173/assets/index-Cn4t-bIz.js:189:391919)
    at Object.start (http://localhost:4173/assets/index-Cn4t-bIz.js:189:392373)
    at Q5.fetch (http://localhost:4173/assets/index-Cn4t-bIz.js:189:396614)
    at $5.fetchQuery (http://localhost:4173/assets/index-Cn4t-bIz.js:189:408418)
    at $5.ensureQueryData (http://localhost:4173/assets/index-Cn4t-bIz.js:189:406764)
    at http://localhost:4173/assets/index-Cn4t-bIz.js:189:385554
    at U (http://localhost:4173/assets/index-Cn4t-bIz.js:187:9722)
    at http://localhost:4173/assets/index-Cn4t-bIz.js:187:9865

💿 Hey developer 👋

You can provide a way better UX than this when your app throws errors by providing your own ErrorBoundary or errorElement prop on your route.