remult VS json-schema-to-typescript

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.

Compile JSONSchema to TypeScript type declarations

Nice! Lots of tricky edge cases to do this right: there’s ambiguity in the JSON Schema spec, version-to-version changes, many popular community conventions that don’t adhere to the spec, etc. Feel free to check out the tests to understand some of these: https://github.com/bcherny/json-schema-to-typescript (shameless plug — I have maintained this library for a number of years).

jsonnet is my go-to language for anything related to configuration, after having tried json, yaml, TS, edn, and tasting dhall and toml. It addresses all problems in the article and more.

the composition strikes a good balance between extensiveness and ease of use.

the generated json leads to easy and portable data, and if you write jsonschemas from jsonnet, tools like json-schema-to-typescript [1] make it easy to import a consistent interface, and almost every language has a reasonably up-to-date validation library.

[1] https://github.com/bcherny/json-schema-to-typescript

Take a look at https://github.com/bcherny/json-schema-to-typescript, too. I used it successfully at a previous job. IIRC, I had to write some code to convert OpenAPI to JSON Schema but it wasn’t onerous

If you're using OpenAPI, you could use this to generate TypeScript interfaces:

https://github.com/bcherny/json-schema-to-typescript

It works really well

I'm messing around with a process to convert JSON schemas to TypeScript interfaces using json-schema-to-typescript. I have a little under 900 JSON files each containing a schema, totaling about 3.5 MB.

json-schema-to-typescript