react-dates VS formik

react-dates An easily internationalizable, mobile-friendly datepicker library for the web.

`ReactDateRangePicker`, gives it's own date picker to use(see ss: https://i.stack.imgur.com/6mkER.png)

This was the case for Airbnb with the popular react-dates project. They tried out solutions and had to change so much code that, at some point, they decided to build their own. The answer to the question of whether to create a component library is, as always, that it depends.

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 .