For a long time, I have been frustrated with the state-of-the-art about the existing ORMs. I like things to be simple, but somehow all ORMs seems to be bloated and overcomplicate a lot of things.
When designing a new project, I have been trying to find a more satisfying design while avoiding the existing ORMs. I especially wanted to use proper SQL rather than reducing it's syntax to fit it in another language.
This is the result of my experiments. This is a completely new balance between productivity, simplicity and readability, while providing useful features.
I use the template-string tagging syntax to allow writing and concatenating raw SQL queries, while keeping it safe from injections, which allowed me to build kiss-orm. There is no query-building involved, you can freely use the full-power of SQL.
I would appreciate feedback on this (and contributions if you love it :D ).
"you can freely use the full-power of SQL"
Sounds like Dapper from the .Net world - which I like precisely for that reason:
OP's project is a little more opinionated than Dapper in that it defines repositories and whatnot. Dapper's more like just a set of query extensions that support basic object mapping. I love it personally, but I wouldn't even call it a micro-ORM.
It might be a good idea to focus on the use of template strings for safe and handy SQL generation instead of introducing too many opinionated ORM concepts.
If one had to, i'd separate these things in different libraries and let the developer opt in to what he needs.
[0] https://github.com/gajus/slonik-sql-tag-raw
[1] https://github.com/felixfbecker/node-sql-template-strings
[2] https://github.com/blakeembrey/sql-template-tag
[3] https://www.npmjs.com/search?q=sql%20template
Edit: When I first read your comment, I thought you were saying that you wanted a separate library just to have the SQL template functionality.
I agree with what you're saying though.