I’ll echo what @jfrolich says - probably a good idea to go to v11.1.x but stay on curried, and then move to v12 and uncurried when v12 has shipped as stable and the relevant parts of the ecosystem has adapted to it. Most of the widely used packages are already uncurried ready, so going to v12 is just a matter of dropping the dependency on @rescript/core since that’s now integrated into the compiler. But there are a few exceptions of course, where the migration to uncurried hasn’t happened yet.
↧
Curried/uncurried single-argument functions
↧