stripe-sync-engine VS Passport

For everyone in this thread that use ORM for migrations, which seems like rather heavy handed approach, have a look at https://github.com/supabase/stripe-sync-engine/blob/main/src/utils/migrate.ts which is how you can easily implement migrations without all the ORM overhead/bullshit.

Stripe-Supabase Sync Engine: syncing the stripe database to supabase would’ve been nice but also would’ve been a lot of unnessary extra work (I’ll just use stripe webhooks instead). Also, I needed to spin up something to host that and I wasn’t willing to do that.

I've heard good things about Supabase, but I haven't used it myself. If you're in a position to deploy the DBMS and backend software yourself, you could consider setting up PostgreSQL and a gRPC server service yourself. You can even write the server service in Dart.

For those who need a clickable link to the project: https://supabase.com/

Supabase account

If I want to build micro-saas then are one options from above feasible? or should I go with supabase? https://supabase.com/

Next, use something like https://www.npmjs.com/package/passport, this is authentication middleware, and it works similarly for different authentication providers. Carefully read the documentation. OAuth is complicated, but that's because it solves a complicated problem

Passport is outdated and the project has been more or less on a stand-still for years now. As of currently, there are more than 320 open issues and very few have been resolved within the last months. I'd highly advice you not to use Passport for your applications in 2023. You've received some great alternatives by others in the comments here.

lib: The lib folder, short for "library", is mostly used to store the actual source code of the package, but it can also be used to store third-party code, utilities and helpers. Example from passport.

Research - there's github and stackoverflow documentation saying this is part of passport.js 0.6.0 that can be resolved by turning logout into a callback function (I was not the first person to encounter this error).

passport for authentication

I went down the rabbithole of using next-auth (now authjs) for a recent project. Having used Passport.js [1] for Oauth2 the last time I was doing node.js ~3 years ago, I found this library to have many footguns as comments/answers on SO and Github.

Seems like many people are trying to shoehorn their codebase [2] (!!) to make it work with the way the library manages sign-in flow, redirects, cookies, logout, etc. [3]

These were solved problems in the MEAN stack era with middlewares, but now that Next.js/react is the trend, people are doing everything they can to make it work - from relaxing security configs, to stashing things in the JWT just so some callback can get an additional piece of data.

[1] https://github.com/jaredhanson/passport

Passport to act as auth middleware to authenticate requests Passport

Checkout using NestJS that uses Passport or just checkout Passport