It's our great pleasure to announce the release of ReScript 11.1!. This release brings a ton of new features and improvements:. - Tagged template literals.- JSX for more than React.- Native BigInt support.- Array spread syntax.- %todo annotation for incomplete code. and more🎉.

RT @___zth___: Some pretty crazy auto migration utils coming to @rescriptlang v12 if all works out. Primarily to ease migrating to the ne….

We just published the recording of @_binary_search's "Intro to syntax development" talk. Maxim gives an overview of the syntax parser, talks about basic concepts and demonstrates a concrete syntax change in a live coding session!. Link down below ⬇️.

Help us test our new build system which comes enabled by default with the first ReScript v12 beta. npm create rescript-app@next .

RT @___zth___: This is an awesome trick by @dillon_mulroy! . Since I love ReScript, here's the same example but in a functional style since….

RT @asleMammadam: we're doing this for these kinda tweets 💙. thank you the @rescriptlang team and @KrComet for trusting .

Let's go #ReScriptRetreat2025!. Thanks to for supporting us to get everyone together to work on the ReScript language and tooling. Goal for this weekend: Get ReScript v12 ready for production and talk about the roadmap for 2025🚀

RT @WoonkiMoon: Introducing Bibimbob: See your ReScript module dependencies in VSCode with interactive visualizations!.👉 .

We just landed a new (experimental) feature for v12 - nested record definitions!. Records is a corner stone in ReScript. However, they can't be nested without explicit definitions. Until now!. Will be especially useful for deeply nested records (like options objects).

We are happy to announce that there will be another "ReScript Retreat" in 2025, once again in Vienna, Austria. Check out this new blogpost to get an idea what we did last year.

Our devoted and friendly community is the most valuable asset we have. Here's an example of that as users and library authors work together rapidly to find a pragmatic solution to a concrete problem:

One of our core contributors were on the Developer Voices podcast talking about ReScript - what ReScript is, who it targets, and how it relates to JavaScript and TypeScript. Check out the conversation here:.

It also has the added benefit of making more TypeScript code copy/pasteable to ReScript without requiring breaking each type shape out into its own type definition.

Records are powerful, but you need explicit definitions for them. We're experimenting with allowing inline record definitions nested inside a record type definition. This will make some of the common use cases for records more ergonomic.

The new dot completion also works for objects. Objects are structurally typed, doesn't need a type definition, and are quite useful in some scenarios. Completion for object fields will be more ergonomic and get better discoverability with this addition.

With the new dot completion enhancements in our editor tooling you'll now get completions from the Option module when autocompleting on a record field that's an optional value, instead of just no completions like before.

Together, these features helps both newcomers and established ReScript devs, while increasing the discoverability and usability of essential patterns like using and providing pipeable functions for your various types. We're excited to release this and hope it'll give you value!.

You'll now also get pipe completions when you do dot completion on any type, not just records. And additionally, you can even configure per type to have the editor give completions from additional modules, not just the module it belongs to.

For newcomers, one of the differences to JS is using pipes where you'd normally use method chaining. This takes a bit of time to learn. To fix this, you now get pipe completions from dots as well. So the experience is like in JS, but an actual pipe is inserted on completion.

Happy new year!. We're almost ready to release an exciting editor feature - dot completion everywhere!. "." will now trigger completions for more than just record fields. Example: you'll get completions for pipeable functions from the module of that type. Examples and videos ⬇️.