commerce VS next-auth

There are several open source solutions if you're interested... you can do a headless frontend with Vercel Commerce (Next.js) and use any of the supported e-commerce backends to manage catalog/cart/orders/etc: https://github.com/vercel/commerce

You need to use Medusa or Saleor as the backend (they are open source headless ecommerce backends). There already exists an amazing boilerplate and fully functional app for both of these: https://github.com/vercel/commerce

Hey everyone, I stumbled upon an intriguing website recently, built using Shopify, the platform notorious for its sluggish performance. However, to my surprise, this particular site managed to achieve a perfect 100 score thanks to NextJs. I know this community is well-versed in website performance, so I thought I'd share it with you all. To be honest, I've been pondering the significance of speed when it comes to the success of online stores. Can a few milliseconds really make or break a business? We often hear the phrase "Milliseconds Make Millions," and I wonder if it holds true in reality. What are your thoughts on this? In today's digital landscape, it seems like everyone is using Shopify, making it the go-to platform for setting up an online store. But is being the fastest fish in the pond the key to outperforming the competition? Does speed truly matter when it comes to customer experience and ultimately achieving financial success? I'm genuinely curious to hear your insights and experiences regarding the impact of website speed on online businesses. Do you believe that optimizing every millisecond can lead to substantial gains, or is it more of a minor factor in the grand scheme of things? Let's have an open discussion about the role of speed in the success of Shopify sites and how it aligns with our experiences and beliefs. I invite you to share your thoughts and contribute to this conversation. No sales pitches or hidden agendas, just an honest exploration of the topic. Looking forward to hearing your perspectives! Best regards, CuriousRedditor

Next.js has an official e-commerce template here: https://github.com/vercel/commerce

This is great, especially as Next.js commerce has decided to go shopify only - https://github.com/vercel/commerce/pull/966 - making a full open-source solution impossible.

Vercel also have an example for it. https://github.com/vercel/commerce/tree/main/packages/swell

Vercel Commerce

NextAuth.js is not perfect. One of the shortcomings is that it currently does not implement federated logout. This means that even if a user signs out of the Next.js app, he does NOT get signed out of the Cognito user pool client. As a consequence, the user is not really being logged out (i.e he is able to login again without providing the credentials). You can read more about this problem in this Github thread.

NextAuth for adding auth

Let's learn a bit about Descope and how to use it with Auth.js (next-auth) to protect our Next.js app with role-based access control (RBAC).

https://github.com/nextauthjs/next-auth/issues/5647#issuecom...

Next Auth CognitoProvider Internal Library: https://github.com/nextauthjs/next-auth/blob/v4/packages/next-auth/src/providers/cognito.ts

I mentioned this in an age-old discussion on NextAuth GitHub repo.

Authentication is a fundamental part of most web applications. Integrating authentication into your Next.js app can be simplified with NextAuth, a powerful authentication library that supports various authentication methods. However, the documentation around setting up NextAuth with the "Credentials" auth provider might not be as clear as you'd hope. My implementation is greatly enriched and partially based on Next-Auth docs and the following github thread.

For Auth: https://authjs.dev/ - works like a charm with Svelte https://authjs.dev/reference/sveltekit

NextAuth.js

I'm surprised nobody mentioned https://authjs.dev/