svelte-headlessui VS next-auth

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

You mention YAGNI, but I think the bigger blocker is "Don't reinvent the wheel" - which I think is the most misunderstood bit of programming advice out there. In my SvelteKit app, I am not using a "UI Framework" that provides components to me. I don't need to. Svelte is simple enough that I can build almost anything myself. I've looked at Skeleton's source code, and their components on average are not better than versions I have rolled myself. There are a few cases where it's better to use a framework. Sliders, for instance, have a lot of edge cases. So I use Swiper for carousels. But even then, I could build a working basic slider (that doesn't address the numerous edge cases) myself in an hour. The other case is Headless UI but even there, I disagree with how he implemented some things and it's possible to roll your own Svelte Headless UI just from Tailwind's source.

I've been using https://github.com/captaincodeman/svelte-headlessui/ since previous with react I was using headlessui w/ tailwid.

I've also seen this alternative library utilising svelte use:action directive rather than components.

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/