pg-promise VS next-auth-example

Personally with more time I would also use JavaScript so I can improve it. Last time I wrote something with Express and a database connection is a long time ago and not for work, only for my personal testing. But for JavaScript database connection to PostgreSQL I recommend pg-promise. That works like a charm.

I've always loved this project / product:

https://github.com/outline/outline

I think the guy who built it posts here. There's also pg-promise, a "Postgres interface for Node.js":

https://github.com/vitaly-t/pg-promise

Raw pgPromise with string templating.

i do have a couple of them like websocket server using ws, bullmq for sending emails and postgres listen/notify to push data to websocket clients. Would you happen to have any ideas on how to go about these? I did some research

Yes. You can also take at the pg-promise library. https://github.com/vitaly-t/pg-promise

Is there any difference to the named parameters already supported? https://github.com/vitaly-t/pg-promise#named-parameters

During my years as a dev i have really started to dislike ORMs. They always fail in the end. SQL is universal, and transfers between languages and tech fields. This is why im pro-sql, and always try to avoid unnecessary abstractions.

I have actually went back to writing pure SQL in files, and using those as params for whatever db engine i use, this makes it even possible to reuse the code in other projects (even its unlikely that you can use the exact same query, but just as a "it would work" in theory).

For node based projects i have used and would probably still choose pg-promise (https://github.com/vitaly-t/pg-promise).

Since I'm decent at writing SQL queries and I don't want to learn additional syntax to work with ORMs/query builders, I stay as close as possible to the database driver. pg-promise is an excellent library built on top of the Node.js driver for PostgreSQL. It's built with promises in mind, it's well-tested and typed.

dont believe me? look at how many open issues they have https://github.com/vitaly-t/pg-promise/issues

I just used pg-promise - it handles the connections for you, up to you to write the SQL.

https://github.com/nextauthjs/next-auth-example https://next-auth.js.org/getting-started/example https://next-auth.js.org/configuration/initialization#route-handlers-app https://www.prisma.io/docs/getting-started/quickstart https://authjs.dev/reference/adapter/prisma

This is not true in the slightest. Just one example: https://github.com/nextauthjs/next-auth-example/blob/main/components/footer.tsx

Looking at the example repo for using next-auth (https://github.com/nextauthjs/next-auth-example), how would I add a provider to the [...auth].ts file so that I could have a user login with email and password, hit my FastAPI authentication endpoint, and resolve with the token if authentication is successful? Do I just use the Credentials Provider? https://next-auth.js.org/configuration/providers/credentials

If you want a full-featured authentication system with built-in providers (Google, Facebook, GitHub…), JWT, JWE, email/password, magic links, and more… use [next-auth](https://github.com/nextauthjs/next-auth-example).

Just use (next-auth)[https://github.com/nextauthjs/next-auth-example], and without setting up a db it automatically defaults to JWTs. Only thing that I would do is make sure to setup a revocation policy on the server that allows you to revoke JWTs before its expiration. I usually keep a simple json document of revoked tokens, which I can then deny access to in-case the token was ever compromised.

I see in the official example app,

First we need to clone example app from next-auth. You can find the whole guide from next-auth here or just follow my steps.

The gist of it is actually covered by the next-auth example app: https://github.com/nextauthjs/next-auth-example/blob/main/pages/api/examples/protected.js