People who don’t know anything about auth but have general programming experience

Wait the latest is v7???

(I also met @danabra.mov but we had like zero things in common so it was an awkward handshake lol)

けどやっぱり

serve(handler)

が

serve(options, handler)

になるのは好きじゃない

昨日終わった後気づいた

serve(options, () => {
// めっちゃでかい関数
})

vs

serve(() => {
// めっちゃでかい関数
}, options)

上の方が綺麗

ん、フォーマッター？？？

個人的にResponse以外使えるのはどうかなーって感じ

標準ライブラリはやりすぎない方がいい気がする

I also think it's a nice bonus that it's self contained. It's super clear where the line is between your code and the library/package code

- vs SaaS: This is obvious but your users are stored in your db + no predefined schema to follow
- vs better-auth: You can fully customize how you create/delete/get users and even use db transactions. (Personal preference but) I don't like a library doing migrations + handling connections directly

Link: faroe.dev

Right now, I have the backend portion mostly done as well as the API client. You still have to make the UI and deal with some client state so it'd be nice to have packages for js frameworks, but that's not something I want to deal with right now

I was using SQLite here but it'll work with anything. You get full control of the user table and you add additional columns and create relationships with other tables

But essentially for the client side you just have to call createSignup(), verifyEmailAddressVerificationCode(), etc

The more interesting part is the backend, which I'm not going to share just yet

It'll be focused on email/password so it won't support social logins via oauth/oidc at least for the initial release. I do have plans to add 2fa and eventually enterprise sso but I want to get the basics right first