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.
The dev server is slow. Coming from Vite to whatever NextJS is using is just painful.
Facing some open issues while developing. There's a specific one where redirecting does not work if there are different root layouts. We have a landing section, an auth section, and a dashboard section that all use different layout so they had to be grouped. When a user signs in and has to be redirected to the dashboard, it doesn't worker due to the different layouts. I had to return an object with a success boolean and redirect on the frontend using useRouter instead of the redirect function.
Endless Hydration errors that I sometimes don't even know where they are coming from.
Peer dependencies warnings and errors using npm because well NextJS is bleeding edge and uses React 19RC. But I guess that's no longer an issue since React 19 is out.
But some things are great.
Server actions make handling forms and form errors easier. I haven't had to use controlled forms so far. I probably will have to for better UX but so far I don't have the need.
Fetching data in RSCs is great. It simplifies things in a way.
The routing convention using the app router is great. I used SvelteKit a bit and I love how they have specific files that do specific things when it comes to routing. Due to this collocation is easier. Each route can be coupled with things that only it uses like entity definitions, types, services, and components.
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.
A software engineer with 4+ years of experience in frontend development using React, Next.js, TypeScript and Tailwind CSS, with hands-on experience in smart contracts, GraphQL, and multi-chain wallet
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
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
A software engineer with 4+ years of experience in frontend development using React, Next.js, TypeScript and Tailwind CSS, with hands-on experience in smart contracts, GraphQL, and multi-chain wallet
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
I love it, is this your website btw? Really nice experience and the latest stats are very neat. You should check out Vratix btw, I think you will love it
That's something interesting, I've never heard of it, but I will check it out in more detail, thanks. The site is mine :) I was doing the tech breakdown for one of the customers and decided to put it live, hoping anybody else could find it useful.
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
Nice one, you should make it possible for others to publish their tech stacks, similar to StackShare or other websites. Your UI is better as its super minimal and clean
Yh I loved em, I actually use Hono with astro using Astro request handlers, combining them I use the CHAD stack comprising
Cloudflare for cloud services / hosting (cloudflare workers, AI, db D1 etc)
Hono for backend APIs
Astro for frontend
Deno as runtime
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
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 :)
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
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!
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
Founder & CEO of Ace AI - an autonomous cloud engineer for DevOps and SRE teams. Ace makes your cloud infra proactive by catching performance issues and incidents early and recovers from them with AI
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.
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
Mine is a bit different, mostly in favor of Hono and Cloudflare betterstack.me/stacks/dynamic or Astro betterstack.me/stacks/static
I love it, is this your website btw? Really nice experience and the latest stats are very neat. You should check out Vratix btw, I think you will love it
That's something interesting, I've never heard of it, but I will check it out in more detail, thanks. The site is mine :) I was doing the tech breakdown for one of the customers and decided to put it live, hoping anybody else could find it useful.
Nice one, you should make it possible for others to publish their tech stacks, similar to StackShare or other websites. Your UI is better as its super minimal and clean
Thanks! I didn't even know such a tool StackShare exists :D I'm learning new things with your every comment
Yh I loved em, I actually use Hono with astro using Astro request handlers, combining them I use the CHAD stack comprising
Cloudflare for cloud services / hosting (cloudflare workers, AI, db D1 etc)
Hono for backend APIs
Astro for frontend
Deno as runtime
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!
That is great to hear the good news
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.
Where is NestJS ?