rescript-compiler VS ava

If you’re a front-end developer, you should checkout ReScript[1], supposedly a JS-oriented successor of ReasonML and developed by the ReasonML team.

[1] https://rescript-lang.org/

ReScript is "Fast, Simple, Fully Typed JavaScript from the Future". What that means is that ReScript has a lightning fast compiler, an easy to learn JS like syntax, strong static types, with amazing features like pattern matching and variant types. Until 2020 it was called "BuckleScript" and is closely related to ReasonML.

As another commenter has already suggested, ReasonML has a lot of what you described here.

However, modern JS-oriented toolchain for ReasonML is called ReScript and you can learn more here: https://rescript-lang.org/

ReScript (before BuckleScript) https://rescript-lang.org/ is a functional language that can also use OOP. Ideal for Javascript and Typescript projects, React and servers. It integrates perfectly with Javascript and Typescript code https://rescript-lang.org/docs/react/latest/introduction

Thank you!

We invited Gabriel because we think what he's building is pretty cool. It showcases so much about EdgeDB: its type system, data model, query language, composability, introspection, etc.

I'm not a ReScript user myself. What I know is that it's a functional programming language somewhat heavily inspired by OCaml. Their website goes into details [1]

[1] https://rescript-lang.org/

You might want to look into ReScript (https://rescript-lang.org/). It has strong static typing with type inference, and it is very fast.

This is because a “Tagged Union”, another word for TypeScript’s Discriminated Union, is a way to “tag which one is in use right now… we check the tag to see”. Just like when you’re shopping and check the tag of a piece of clothing to see what the price is, what size it is, or what material it’s made out of. Languages like ReScript compile many of their Unions (called Variants) to JavaScript Objects that have a tag property.

ReScript is "Fast, Simple, Fully Typed JavaScript from the Future". Let's take a look at how we can add it to an existing React project.

REscript

Ultimately, Dhall wasn’t verbose enough nor was I Dhall ninja, but something like TypeScript or ReScript probably would have been better.

We use Jest Framework for testing. Jest is not a dogma, and, of course, in its place can be any other test runner, such as Mocha or Ava. Let's focus on tests. I'll provide a short example because I don’t want to waste your time. You can find the full version here. It's crucial to read the comments in the code below. Let's go!

> In the popular jest test runner, each test file is executed in its own child process.

Is that confirmed?

I've been following this issue:

https://github.com/jestjs/jest/issues/6957

And what Jest actually does is still kind of muddy.

In contrast to that, other test runners like AVA have a clear description what happens when:

https://github.com/avajs/ava/blob/main/docs/01-writing-tests...

I've been looking at using japa or ava for web server testing but was curious what others were using and why.

Continued work on the test suite. Implementing AVA, with snapshotting. Making a lot of effort to have the snapshot directory structure match the test262 test directory structure by generating AVA test files.

You might want to give ava a spin:

https://github.com/avajs/ava/

It has a TAP reporter, but more importantly, as opposed to the more popular solutions, like Jest, the way it achieves parallelism is explained in the docs and won't change anytime soon, thus preventing wonky, hard to debug errors which occur when this part is abstracted away.

I switched to ava for that reason and have been very happy with it. But vitest looks nice, too. Thanks for the pointer.

Runs unit tests using AVA.

Last but not least important are ava, uvu and tape; they are a really light and fast test runners.

I've had some good experiences with Ava + Sinon. I've personally disliked Jest because it seemed to do some weird trickery in the background that prevented me from using ES modules.

Ava for a simpler environment than Jest, which I usually use. I need to check how to mock ESM with it, though.