Back
Lovabase
Lovabase
#lovabase
The world's most advanced front-end ORM, self-built. Also houses homegrown auth, payments (Stripe integration) and . I use it for 5 of my projects: Artiry, Tutoic, PromptGrid, Happenlist and CultureTest.
Why most advanced frontend ORM in the world?
- Type-safe live queries (query types with code generation)
- Optimistic updating of all active queries from any CUD mutation in the application
- Type-safe w.r.t. joins (join-fetching related entities also expands the result types)
Built-in write-ahead-log mutating
- Extremely minimal rerendering when queries update
- Rapid mutations intake (e.g. every keypress) causes no performance issues due to built-in write-ahead log (WAL)
- Seamless integration of optimistic frontend-originating updates and data updates coming from the server
Made it work for both SPA React apps and NextJS apps.
Why most advanced frontend ORM in the world?
- Type-safe live queries (query types with code generation)
- Optimistic updating of all active queries from any CUD mutation in the application
- Type-safe w.r.t. joins (join-fetching related entities also expands the result types)
Built-in write-ahead-log mutating
- Extremely minimal rerendering when queries update
- Rapid mutations intake (e.g. every keypress) causes no performance issues due to built-in write-ahead log (WAL)
- Seamless integration of optimistic frontend-originating updates and data updates coming from the server
Made it work for both SPA React apps and NextJS apps.
added "nulls first" and "nulls last" control to the query api of the most advanced frontend ORM in the world 
#lovabase
added to #lovabase that you can turn early from a query hook with anything other than a query, and the result will carry this value, and it will also reflect in the hook's type. Calling them "pre-query results".
solved a fundamental issue in #lovabase's backend-data-sensitive useEffect hook that caused it to run twice, solving bugs and giving a big performance boost in 
#happenlist's backoffice among others. should probably add some tests to #lovabase so that regressions like this don't happen but meh
i librarized my whole homegrown frontend Auth-, Stripe connection- and ORM (the world's coolest) earlier this year, and today moved one of my Create React App apps to it (in replacement of a having a copy-paste of it in its own codebase, as i used to do everywhere). That system which I call #lovabase is now compatible with both partially-server-side rendered and single page react apps. I was able to delete a *lot* of code today, while performance grew (I made a few performance improvements to the library version of Lovabase since my last sync of all the copy-pastes in the different codebases).