fartscroll.js VS genType

We have types at home.

My litmus test regarding whether I can even consider using a library in production is: does it have more stars than fartscroll.js?

https://github.com/theonion/fartscroll.js/tree/master

Most of the entries there are below that number, which begs the question: is this really that much of a problem that it mandates the drastic changes required?

I actually don't know if it's even doable, considering TS's structural type system, where the answer to the question "what type is X?" is not straightforward.

The best content produced by The Onion was a JavaScript library to make farting noises on scroll events: https://github.com/theonion/fartscroll.js

As a sort of litmus test I use the number of stars a superset of(or language compiling to) JavaScript has on GitHub and how that compares to fartscroll.js: https://github.com/theonion/fartscroll.js/

By this measure ReScript is still a niche language.

I don't really use ts-belt to be certain, but by looking at the source, it seems that it's using genType, which can generate TS types from ReScript values, and that makes interop work really well.

They discuss this in their docs.

https://rescript-lang.org/docs/manual/latest/introduction#di...

Seems like a type system for Javascript, built with a differing set of opinions than Typescript.

Looks like they also offer some form of TS interop:

https://rescript-lang.org/docs/gentype/latest/introduction

TS Belt has been built with ReScript (and its Belt stdlib). ReScript generates highly performant JavaScript code, and with genType it also automatically generates TypeScript types. Moreover, I've added a few codemods to the building process to provide even more code optimizations and cleaner TypeScript signatures.

To interoperate with TypeScript with proper type information you’ll use third-party genType. Add it as a devDependency and annotate the module export you want to generate with @genType (in previous versions you’d surround annotations with square brackets).