@Burstaholic To some extent, that’s what descriptions and keywords are for; when you search for “key value json” in npm, jbase currently is at the top of the list. So, with creative keywords, we can make sure the project gets found in most searches, and then as it gets popular, it’ll naturally be ranked higher.
On the other hand, something to consider: my target audience is me. I don’t care how popular it gets, I want something with the API that I favor, that just works. That’s why I wrote it. So I can call it whatever I want, really. I’m just a crazy sod who also wants to make this stuff discoverable by anyone who agrees with my designs. XD
To the point: I kinda like that play. I’m just not sure if I want to tie the models lib to
trivialdb that much.
I also agree with @Burstaholic about using the term “backend” instead of “driver”. (I also like it better than knex’s choice of “dialect”, since it involves more than just the query language dialect used to render queries)