As the year comes to an end, I decided to list the tech stack I’ve been using to build my projects. This list covers everything from frontend to ba...
For further actions, you may consider blocking this person and/or reporting abuse
My experience with NextJS has been terrible. I had only worked with React through React Router in the past. I recently started a project at work which uses NextJS and I have to say some stuff has been painful.
But some things are great.
The problem is, these benefits exist in all other similar frameworks e.g SvelteKit. But the problem is the downsides are listed are very specific to Next. I'm sure there are more.
Here’s an interesting issue I ran into with route protection in Next.js,
If you use middleware to guard a route, users can still sneak back to the protected page using browser navigation.
On the other hand, relying solely on client-side protection can lead to some weird hydration issues.
I combined both middleware and client-side protection.
Not sure if it’s the perfect approach, but hey—it worked for me!
Nice, interesting approach tbh, I think it makes a lot of sense to protect from certain edge cases. Interested to see how others are dealing with route protection
How you deal with it?
What’re the best coding practices to implement it?
I've been using middleware mainly. And also I always protect any backend endpoints by checking if the user has a valid JWT access token.
What do you mean by
Thank you
Super detailed, thanks for sharing your experience. I haven't experienced the same issues as you yet, but have you tried reaching out to someone at Next.js/Vercel? They are usually quite responsive, especially on Twitter and the Vercel community.
Might be worth a shot. But yeah I agree that other frameworks offer similar benefits, I haven't tried them out yet. Maybe I will use the Christmas period to check them out!
Thank you
To be fair a lot of these "issues" are because rendering React to static pages introduces some new things that the developer should consider. I've definitely had issues with hydration when using vite and SSR.
I really wish that Nextjs would switch to vite though... Like you said, the dev server is really slow... Next build is pretty slow too actually.
Hi @ivanivanovv , how's your day? I've just try vratix now but I've encountered some error when installing it can you please help me out. Thanks
Hey @yugeroh, we just released v1.0.8 of the CLI that fixes the Windows bugs. Let me know if it works for you and what you think of Vratix after you try it out :)
Nice! It works fine now. Thanks @ivanivanovv for letting me know. Awesome project BTW
Thats great to hear! Looking forward to the projects you start with Vratix. btw we have a Discord community, you can join it to discuss anything backend related!
Hey Oliver! Thanks for reporting it, I resolved this issue yesterday. Will publish a fix today! Sorry for that, will let you know once live :)
Thoughts on Firebase? It’s used where I work currently.
I've used it before, but if I go for a NoSQL database it will be MongoDB. I find all Google services a bit weird to setup and configure. Haven't used Firebase in ages so that might have changed.
PostgreSQL is just a solid choice for anything production-level.