Live data from Hacker News

Better Auth – Authentication library for TypeScript

better-auth.com

1–10 of 37 posts

Re: Better Auth – Authentication library for TypeScript

#3

[flagged]

Auth.js is not made by Vercel. Quote: “ The Auth.js/NextAuth.js project is not provided by, nor otherwise affiliated with Vercel Inc. or its subsidiaries. Any contributions to this project by individuals affiliated with Vercel are made in their personal capacity.”

Re: Better Auth – Authentication library for TypeScript

#4
As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but this new wave of of SSR-led full-stack frameworks is tricky.

Re: Better Auth – Authentication library for TypeScript

#5

[flagged]

Auth.js isn't really by Vercel even if they scooped up the creator and stuck one of their "powered by" stickers on it... it does have a fun tie-in with Rauch's cartel though

Clerk sponsors it extremely heavily so that when you get fed up with dealing with it, every single page has a CTA funneling you to them.

Honestly the whole situation has a terrible terrible smell, but that's post-Rauch JS for you.

Re: Better Auth – Authentication library for TypeScript

#6
post #3

[flagged]

Auth.js is not made by Vercel. Quote: “ The Auth.js/NextAuth.js project is not provided by, nor otherwise affiliated with Vercel Inc. or its subsidiaries. Any contributions to this project by individuals affiliated with Vercel are made in their personal capacity.”

You're not wrong but it's a very understandable mistake when the footer has a big old "powered by Vercel" logo and the creator works for them.

The logo is probably just supposed to another opportunity for them to grab mind share by hosting the site for free and sticking that there, but it creates a confusing impression.

Re: Better Auth – Authentication library for TypeScript

#8
post #4

As someone developing with both Nuxt and Next, I find these "full-stack" JavaScript libraries and frameworks really confusing and difficult to grok. I understand the benefit of only having one ecosystem to worry about (JS/TS in Node and browser) but I'm not convinced that having backend and frontend in the same codebase is actually a good idea. It might be due to being a more "old school" full stack developer, but th…

I started a side-project in SvelteKit a while ago, and so far I still like it a lot. When I saw what projects using it look like, it somehow just intuitively 'made sense' to me. For me it's also just the right amount of 'magic' so that it's still quite flexible, but takes care of the parts that would be tedious otherwise.

(I've never worked with Nuxt or Next though, so I can't directly compare them.)

Re: Better Auth – Authentication library for TypeScript

#9
Looks interesting. I like that you can plug your own identity provider quiet easily. One nit: They should really rename their Node integration to Express integration because that’s what it is looking from examples (and that’s what people might commonly look for).

Re: Better Auth – Authentication library for TypeScript

#10

[flagged]

Hey, author of Better Auth here. I created Better Auth because I couldn’t find any other auth library that goes beyond simple login with OAuth. Even then, the only properly maintained ones were NextAuth (Auth.js) and Lucia (which is now deprecated). I’m not sure where the idea of "too many auth libraries" is coming from.
Post reply on HN