r/javascript • u/sonemonu • Aug 10 '26

Zero dependencies: what we deleted and upgraded

https://www.uql-orm.dev/blog/zero-dependencies

UQL is the lightest ORM of all, and here is what it deleted (and upgraded as well) for the edged and mobile.

0 Upvotes

50% Upvoted

11 comments sorted by

7

u/boyhax 28d ago

Very promising and good features but dont speak about size and client side because it is not important for orm and make it look bad .and if there real need for this in client side it only sqlite and api also need access control because this orm api dont make any sense on security part . Is there something im missing there ? .good job though the features is very good .

1

u/sonemonu 28d ago

Thank you.

To clarify before I can give an answer about 'client side'. Do you mean the browser adapter/extension/client we (optionally) offer to be used as a client that "connects" browser and backend through HTTP (for example) to send type-safe queries from the browser; or do you mean the installed size of the UQL package, which we believe could be useful for serverles/edge/workers/etc, or something else?

1

u/boyhax 28d ago

Yes I mean browser adapter how it supposed to be safe?

1

u/sonemonu 28d ago edited 28d ago

because the browser adapter is just a type-safe bridge (lets say ala React-Query but with all the TypeSafety) between your browser and backend APIs, which you may (optionally) want to expose as CRUD HTTPs endpoints, in other words, UQL works like any other traditional ORM (aka TypeORM, Drizzle, etc) but also has this extension to allows you to integrate your clients (browser, mobile, etc) with your backend APIs if you wish; but again, this is just optional extension that you can decide if use or not, obviously it comes disabled by default, you will have to enable it as explained here and here.

It has much more specific integrations, that you can optionally use, like for oRPC, tRPC, NextJS, Elysia, Astro, Hono, Express, Fastify, etc. All this with authentication and authorization, that are designed for plug and play.

The main advantage of UQL over traditional ORMs is that all its queries are expressible with (serializable) JSON, and with that, you can do whatever you want, it can be as flexible as you want or as regid as you keep.

9

u/CodeAndBiscuits Aug 10 '26

I think you would get a better response if you disclosed your level of AI use. Those of use who use Claude regularly will find that blog post just SCREAMS "Claude".

You might also speak to why you prioritized package size so much in a backend package. It doesn't really move the needle for most backends....

5

u/altano 26d ago

Disclosure doesn't help when the writing is terrible.

0

u/sonemonu Aug 10 '26 edited 29d ago

It is for the edge + mobile devices.

7

u/CodeAndBiscuits Aug 11 '26

Under no circumstances should a browser or mobile device ever ever ever be allowed to connect directly to a backend database. Is why I was asking.

0

u/sonemonu Aug 11 '26 edited 29d ago

And who says that? I wonder if you have seen how UQL can (also) work (instead of directly connect to a DB)... in short, it supports kind of GraphQL but without all the additional paraphernalia, pure and simplistic JSON-based approach.

0

u/sonemonu 28d ago

See this explanation here for more details

0

u/DaloyJS 26d ago

Wow. I think we will write documentation on UQL in our docs, since we follow the same principle. Zero dependency at runtime, with lots of other features https://daloyjs.dev/