Replies: 2 comments 3 replies
-
From my point of view, if you don't need any special processing and you just handling basic CRUD operations, then using Using server would start giving sense if you have for example some server middleware for auditing all requests or when you need to treat outgoing requests somehow before sending them to an external network (add some headers, alter URL, or whatever). |
Beta Was this translation helpful? Give feedback.
-
Hello, First of all, choosing between these approaches depends heavily on the scalability and specific needs of each project. Personally, I prefer using the server directory. This approach helps keep the code synchronized and takes advantage of the flexibility that Nuxt offers. You can easily manage the server-only parts of your application, from API endpoints to middleware. If you’re working on a project management application, scalability will hit, and you'll likely encounter various obstacles. Pushing for the server directory allows you to structure your endpoints in a way that supports scaling and efficient management. So, that's my perspective. Use the server directory to its fullest potential to ensure your application can grow and adapt to future challenges. Read more about server dir as well, you'll have a better view and approaches, it might not be what you need! |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I want to build a full-stack application using Nuxt 3 and Supabase. we have a server folder in Nuxt3 should I use that? I'm using the Nuxt 3 Supabase module to communicate with the Supabase database. I can fetch or add data to tables in three was:
which approach is best to be implemented? why should I use the server folder? why not?
Beta Was this translation helpful? Give feedback.
All reactions