react-transition-group VS react-intersection-observer

The two most popular choices now (circa Jan 2024) are React Transition Group, started in 2016, and Framer Motion, started in 2018. I'm not too familiar with the former, so this article solely dives into the workings of AnimatePresence from Framer Motion and how it's able to enable exit animations.

We use the React Transition Group CSSTransition. I think you could also use Framer Motion, but I've never really tested this.

With transitions that come out of the box with React do you mean React-Transition-Group ?

I don't have an answer to your specific question but I do have a recommendation that might help. Take a look at https://reactcommunity.org/react-transition-group/. It's very popular and used by MUI in their animated components. Even if you don't install it, looking at their docs and source code might help you get a better idea of how to do what you want.

Oh, but not React; React wants you to suffer! (unless you use a library like react-transition-group, of course.

React-transition-group

There are a bunch of animation libraries to overcome this difficulty. The most famous is probably React Transition Group. There are also Framer Motion, React Spring, and Transition Hook.

AutoAnimate makes for a smooth experience when an element changes in the DOM. I would like to compare AutoAnimate with React Transition Group, which is a simple transition library for component entering and exiting, but with some additional configurations.

Some React animations libraries, like react-transition-group and transition-hook, animate elements with manually configured CSS transitions. Framer Motion takes a different approach, by animating elements under the hood with preconfigured styles.

React Transition Group offers a straightforward approach to animations and transitions by providing its in-built components such as TransitionGroup for defining animations.

1. Install react-intersection-observer from Github

Alternatively, we can use a library that is designed to handle this functionality. This is the approach that we’ll follow in this article. We’ll be using the react-intersection-observer library, which is a React implementation of the intersection observer API. This library provides Hooks and render props that make it easy to track the scroll position of elements on the viewport.

This would do it for ya if you don't want to implement it yourself https://github.com/thebuilder/react-intersection-observer/blob/master/src/useInView.tsx

I'll use React-Interception-Observer to control the screen events you can check the documentation if you wanna know more.

I'm going to be using react-intersection-observer library, which uses native IntersectionObserver underneath and gives us neat hooks for ease of use.

There is no way you didn't see this package before building your own : https://github.com/thebuilder/react-intersection-observer

TL;DR; You can reduce the number of queries you make on listing pages by loading content as it gets displayed. Use react-intersection-observer to detect when an element becomes visible and react-content-loader to display a contentful placeholder loader.

*react-intersection-observer *— react implementation of the Intersection Observer API to tell you *when an element enters or leaves the viewport *(from official description). Docs here: https://github.com/thebuilder/react-intersection-observer#readme

I eventually ended up combining react-intersection-observer and react-content-loader to create a progressive loading experience where elements get loaded as they become visible to users.