gsap-react

Prevent GSAP memory leaks in React by using the useGSAP hook from @gsap/react to automatically revert animations and ScrollTriggers when components unmount or re-render.

GSAP causes Next.js hydration errors when it executes during server-side rendering. Implementing SSR safety patterns ensures GSAP animations only run on the client, preventing hydration mismatches.

Scope GSAP animations to a specific React component by using gsap.context and contextSafe to ensure event-driven animations remain memory-efficient and properly scoped.

Yes, you need @gsap/react to use GSAP in Next.js for managing animation contexts, ensuring automatic cleanup, and preventing memory leaks during component re-renders and unmounting.

The best way to set up scroll-triggered animations in React is using the useGSAP hook, which provides lifecycle-aware cleanup and context management to ensure performant UI transitions.

GSAP animations break on React component re-renders without proper cleanup. Using useGSAP and gsap.context ensures animations are reverted and re-applied safely during the component lifecycle.