nestjs-auth-graphql-mikroorm-starter VS slonik

GitHub - Jenyus-Org/nestjs-auth-graphql-mikroorm-starter: A NestJS boilerplate with authentication, GraphQL and MikroORM.

Well, the best I can offer is the NestJS starter that I go over in the third blog post I linked. I have two implementations of it, one using TypeORM and one using MikroORM. Other, more complex, projects unfortunately aren't open-source for the time-being, but they all implement the same patterns that I went over in the posts.

The good thing about NestJS at least is that MikroORM has a great integration for it. It may not be first-party but at least it's almost a drop-in replacement for TypeORM and I'm really hoping it starts doing well. I've also started to transition to it for my company and have been working in a boilerplate for this setup if you're curious in checking it out.

I see, thanks! I'm actually working on implementing that in my MikroORM NestJS boilerplate which is a copy of my TypeORM version of that. I'm mostly just a little worried about production performance and stability, but at least MikroORM uses KnexJS under the hood so I have a very familiar query builder to work with if issues arise whereas TypeORM's query builder isn't that great IMHO.

And sometimes invest instead in learning a technology rather than hide it: for example slonik encourages you to write normal SQL queries by making SQL templating easier and safer. In turn, your IDE would be able to understand those queries and give you support based on the database schemas you actually have.

I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:

You can already use postgres with Slonik.

https://github.com/gajus/slonik#user-content-slonik-how-are-...

It is not going to be the default because it is way slower.

https://github.com/gajus/slonik/actions/runs/6616647651

Test node_version:18 test_only:postgres-integration is taking 3 minutes.

Test node_version:18 test_only:pg-integration is taking 38 seconds.

For those uninitiated, Slonik is a battle-tested SQL query building and execution library for Node.js. Its primary goal is to allow you to write and compose SQL queries in a safe and convenient way. Now, let's see how it pairs with Express.js.

I am the maintainer of Slonik and I am trying to understand what portion of this sub-users are using Slonik vs other libraries, and if they are using anything else – what are their reasons for it.

It's nice that they implemented string templates essentially exactly the same way Javascript template literals and tag functions work. They even give an example of using it to create a prepared statement (e.g. DB."SELECT * FROM foo WHERE bar = \{inputParam}") which is exactly what many NodeJS libraries due, e.g. Slonik https://github.com/gajus/slonik, like sql`SELECT * FROM foo WHERE bar = ${inputParam}`;

I've found libraries like Zod useful when interacting with external data sources like a database. Slonik[1] uses Zod to define the types expected from a SQL query and then performs runtime validation on the data to ensure that the query is yielding the expected type.

I don't think it's necessary to use Zod/runtime validation everywhere, but it's a nice tool to have on hand.

[1]https://github.com/gajus/slonik

Demonstrate how easily and accidentally one can make an SQL injection with these:

https://github.com/porsager/postgres

https://github.com/gajus/slonik

Have you tried Slonik (https://github.com/gajus/slonik)? It won't generate types from queries automatically, but it encourages writing SQL vs. a query builder and allows type annotations of queries with Zod. Query results are validated at runtime to ensure the queries are typed correctly.