unobin VS io-ts

I'm working on tool called Unobin that lets you write Ansible-esque playbooks and compile them to a standalone binary with all of the templates and files baked in.

I'm trying to solve the "works on my machine" problem that's very prevalent in the devops world. One person's playbook (or Terraform module or Chef cookbook or whatever) works fine on the developer's machine due to assumptions made during the development. But transfer that code to another machine and it's a whole 'nother story. There is often a lack of rigor around dependency management and versioning, along with hidden dependencies such as programs that need to exist on the machine where the playbook is run. I want to make it possible to include all of the dependencies directly in the binary, so you truly need just one binary (unobin) to download and run.

I've made a lot of progress and have what I feel is a solid POC at this point. It lacks many modules but I'm just writing them as I need them. Right now I'm working on a reference playbook to build a Concourse CI stack, and that's giving me solid feedback to myself about what's missing.

https://github.com/cloudboss/unobin

Qué rico. Si tenés chance meté un proceso de code review fuerte, y para el tema de I/O probá a usar https://github.com/Effect-TS/schema ó https://github.com/gcanti/io-ts que les da una solución obvia al tema de "tipos para lo que devuelva el backend", aunque es en realidad mucho más capaz que eso.

My fave is still io-ts (https://github.com/gcanti/io-ts/blob/master/docs/index.md) as I find it more flexible than zod at the ingress. The author is also working on the Effect ecosystem which also looks interesting.

I’ve been using io-ts for this and been very happy with it. [1] It’s similar to Swift’s Coding protocol in case you’re familiar.

[1] https://gcanti.github.io/io-ts/

Yeah, there are a few new concepts and it's not the easiest to pick up right away. The best introduction is here on the main documentation page.

We use https://github.com/gcanti/io-ts/blob/master/Decoder.md which has a very similar interface. It can even be used to mutate the data using https://github.com/gcanti/io-ts/blob/master/Decoder.md#the-parse-combinator.

A good way to significantly improve the reliability of your app is via improving type-safety by moving away from using any to unknown. One relevant example could be when you type your backend responses and when stringifying JSON to using unknown combined with some sort of runtime type checking. It can be done either by using built-in functionality like type guards or using an external library like io-ts, zod or yup.

Usage of TypeBox is similar with io-ts and zod, but it is much powerful and faster than them. Also, TypeBox can generate JSON schema very easily. Therefore, if you're looking for a validator library for new project and not suffering from legacy codes, I think TypeBox would be much better choice than io-ts and zod. TypeBox can totally replace them.

This check can be done with different libraries like: io-ts, typebox, or zod. These libraries allow you to create objects that represent your typescript definitions. Then, these objects can be used at runtime to validate the received data, in addition, you can also convert this object to a Typescript definition to have all the benefits of using typescript. These objects can be called schema validations because they are responsible for the data validation.