rxjs-ninja VS typed-graphqlify

(As you can see from my previous side project it was back in Feb 2021 and then it was sort of abandoned https://rxjs-ninja.tane.dev/)

For example the effort to update this library would mean now I'd have to update through TS version as a migration - trying to update to the latest just makes the code a huge effort to maintain and it's the reason I've sort of abandoned it.

This is a tutorial, along with a demo, on using the fromWebSerial utility function from the RxJS Ninja libraries. The tutorial is fairly short, but I think this just demonstrates how simple it makes interacting with the web serial API and getting a reactive stream to use with other reactive libraries, which in turn makes it much easier to define and handle different structures to the binary data. It also references a serial bluetooth app that might be useful experiments.

I'm currently working on both Formula and RxJS Ninja and both are very type heavy and export all the comments - for me clear docs are important in a library.

You can check out the source code on GitHub.

How would you compare with https://github.com/acro5piano/typed-graphqlify ?

I find DTO models tightly coupled with the persistence layer very brittle and hard to maintain in general. This is why I wish there was a robust code-first solution that would generate only GraphQL types and helpers and nothing else. There is typed-graphqlify, but I'm not sure how ready it is for production.

I found typed-graphqlify, which looks really promising. It creates GraphQL schema with its own TypeScript DSL. This is similar to the awesome io-ts, which does the same thing for data validation.