Frontend

Anime.js v4 is here.

Web-based animations are so back.

(You HAVE to check out this landing page. 🤯👇)

Anime.js v4 is here.

Web-based animations are so back.

(You HAVE to check out this landing page. 🤯👇)

https://animejs.com

After 5 years in the making, I'm very happy to finally release Anime.js v4, my dream animation library:

🧩 New modular API
⚡️ Highly performant
🖱️ Scroll-linked animations
🫵 Draggables
↔️ Responsive
✨ Additive animations
🪽 WAAPI support

And so much more!

Link below👇 https://t.co/a4WXG94wbT

Julian Garnier

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

https://x.com/juliangarnier/status/1907817228168257854

This to me is what makes a frontend library stand out above the rest – direct side-by-side comparisons with vanilla HTML/CSS/JavaScript.

A developer considering your library should know exactly what underlying built-in API is being abstracted over so they can learn it for themselves.

My cursory impression is it’s basically GSAP, but if it were written from scratch today using the 2025 iteration of web standards, browser APIs and JavaScript tooling instead of what was available in 2012.

That means first-class abstractions on top of CSS variables, individual CSS transform properties like `rotate` / `translate` / `scale`, Intersection Observers, the Web Animations API, full type safety with CSSOM + TypeScript and a bunch more goodies that browsers know how to optimize and are otherwise impossible to facilitate with user-land JavaScript.

https://warpcast.com/darrylyeo/0x79b2ba11

https://warpcast.com/darrylyeo/0x6d64a5f9