Unexpected Application Error!

Failed to fetch

TypeError: Failed to fetch
    at queryFn (http://localhost:4173/assets/index-aKmtwX4t.js:13:384955)
    at Object.d [as fn] (http://localhost:4173/assets/index-aKmtwX4t.js:13:395851)
    at q (http://localhost:4173/assets/index-aKmtwX4t.js:13:391919)
    at Object.start (http://localhost:4173/assets/index-aKmtwX4t.js:13:392373)
    at N5.fetch (http://localhost:4173/assets/index-aKmtwX4t.js:13:396614)
    at _5.fetchQuery (http://localhost:4173/assets/index-aKmtwX4t.js:13:408418)
    at _5.ensureQueryData (http://localhost:4173/assets/index-aKmtwX4t.js:13:406764)
    at http://localhost:4173/assets/index-aKmtwX4t.js:13:385554
    at B (http://localhost:4173/assets/index-aKmtwX4t.js:11:9722)
    at http://localhost:4173/assets/index-aKmtwX4t.js:11: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.