4 ms·
"Luckily doesn't affect any of the sites I'm responsible for, since I hated middleware and most of the Nextjs "magic" features already." This is probably the m
by slowtrek 2y ago
"Luckily doesn't affect any of the sites I'm responsible for, since I hated middleware and most of the Nextjs "magic" features already."
This is probably the most important comment. You don't have to use Next.js, and if you do have to, you don't have to use everything they have in it.
- BoorishBears 2y agoI don't think that's the takeaway.
- slowtrek 2y agoWhat's the takeaway?
- BoorishBears 2y agoOne might suspect the first half of the comment.
- l0gicpath 2y agoThe takeaway is that most people don’t think this way. A large portion of online recommendations for auth in Nextjs recommends middlewares for it. Knowing this, you’d expect a faster response time from the people maintaining the framework and stand to lose the most.
- BoorishBears 2y agoThe Vercel-like auth company Vercel's CEO invested in default recommends middleware for protecting routes: https://clerk.com/docs/references/nextjs/clerk-middleware https://clerk.com/docs/references/nextjs/clerk-middleware You wouldn't get a user's info, but you'd get free reign to explore every page of a product