Best Practices for Handling Non-Existent API Routes in Nuxt3
Hi everyone, I'm in the process of refactoring my project, during which I updated my existing API under /api. However, there seems to be no error or typing for both $fetch and useFetch, indicating that the API route being called no longer exists. What is the best way to achieve this purpose? Is it possible to get a type error for this? Thank you.
1 Reply
yes it is