formik VS ramda

I use Formik in an app of mine, but I wouldn't pick formik for a new React project.

If you've looked into form validation with React, you'll likely have heard of Formik. My first run-in with Formik was at a large company I worked; it was already established as the go-to form library for our projects, and I immediately fell in love with it.

First things first, we'll need to update Supabase to the latest version (v2), and install Formik (+ related dependencies) and the Next.js Auth Helpers:

Formik

Also, FastField doesn't work if you're using the useField hook to create composable fields. The useField hook was set to become more performant in Formik v3, but I'm not sure if v3 will release, and it's open-source software, so no one owes that update to us Formik library consumers.

Here's 8 days ago, there's dozens of these if you do a search

I wonder if any of you used react-hook-form or formik and if you did, what where the struggles that you had? I'm interested in particular scenarios that you encountered. Components that did not really click. Stories where you had to throw everything out and start from scratch, that sort of thing.

Firstly thank you for all your help on other issues through countless forum/github comments! Secondly, this worked a treat - turns out it was an issue with Formik (PR) using a legacy version of deepmerge .

JavaScript is great for point-free programming! Make sure you check out Ramda.js https://ramdajs.com/

It’s fun in the sense that solving a puzzle is fun, but I avoid it for anything I need to maintain long-term.

But it’s good practice for understanding combinators which is useful for some kinds of problems.

This is very cool. I remember I got sucked into things like Ramda going down this functional programming rabbit hole :-)

https://ramdajs.com/

To create our pipeline, I'm going to use the pipe function from the NodeJS ramda library instead of building my own.

Other libraries to check out are pratica and ramda

I recently took ownership of the new types/ramda repo. This repo is re-exported by @types/ramda and is the first step to bringing type definitions for ramda in-house. We're already hard at work correcting major issues, adding full currying support, and general bug fixes

I'm going to be honest. You probably don't need to use currying in JavaScript. In fact, trying to fit it in your code is going to do more harm than good, unless it's just for fun. Currying only becomes useful when you fully embrace functional programming, which, in JavaScript, means using a library like Ramda instead of the standard built-in functions.

Lodash gets so many things wrong I’d rather not see it in most projects. I appreciate a good utility library for JS projects but my go-to choice has to be Ramda[1]. Every function it exports is curried and works great with pipe which enables me to write highly reusable and composable functions in pointfree notation. I have never been as productive with lodash, and I find the functional style easier to read

[1] https://ramdajs.com/

Do note though that ramda is different from rambda. 👍 (Granted they are very similar!)