remult VS nestjs-auth

I really enjoyed reading this post from the creator of a new fullstack OSS framework called remult.dev which I think is super useful.

Check out Remult, and if you like it, give it a star. Let us know what you’d like to see next, and also feel free to contribute to the project.

Hey everyone,

Remult is a full-stack CRUD framework that uses your TypeScript entities as a single source of truth for your API, frontend type-safe API client, and backend ORM.

https://github.com/remult/remult

In this version 0.18 we launched a new core feature - real-time live queries. Using this feature any data fetching done with Remult can easily turn into a live-query subscription that listens to backend changes on its result set and updates the frontend state accordingly.

Any feedback/suggestions would be appreciated.

- Yoni

Now that you’ve learned about Remult, how would you use it in your next project? To learn more about Remult, check out the official documentation.

I can suggest Remult which is "all-code" but handles most of the CRUD for you while you have complete control over the frontend and backend for more complex stuff...

Simple CRUD-based modules, a common requirement of any business, should be simple to build and maintain. Remult is a comprehensive framework that allows developers to build full-stack, type-safe apps using only TypeScript code.

So I spent a lot of time in the Nest ecosystem, and I wrote some nontrivial libraries with a little (not a lot) of uptake (and neither are actively maintained at this point, so these are here mostly for completeness):

https://github.com/eropple/nestjs-auth

https://github.com/eropple/nestjs-openapi3

I was pretty excited by NestJS when I ran into it because, well--I don't mind magic, when it's done right. I quite like Spring Boot, for example. But NestJS's magic is...incorrect, in a lot of ways. The DI container is a little bit scary, with oddly hardcoded ways to register interceptors into request scope (itself necessary because NestJS's logging facilities aren't--or weren't at the time--decorating requests with X-Request-Id or similar, so you had to register your own) and no way to then define interceptor order.

It also has a lot of really overlapping nouns; guards are interceptors but less capable (and @eropple/nestjs-auth didn't use them at all) and the "pipe" concept for validation was itself inscrutable. To make it usable, I ended up just doing everything with decorators and interceptors, all living in request scope. And once I'd gotten it going, it was pretty nice. But it also meant broad incompatibilities with much of the NestJS ecosystem.