There's a moment in every Nuxt developer's life when they stare at their fifth consecutive
onMounted(() => anime({...})) and feel something die quietly inside them.
Nikola Tesla reportedly wept the first time he saw his AC current being used to power a carnival Ferris wheel. Not from pride. From the sheer indignity of the application.
That's the energy.
Then someone built nanimejs — Anime.js composables for Nuxt that let you call useAnimate(), useTimeline(), useStagger() directly in component setup. No lifecycle hook scaffolding. No apologetic onMounted wrapper. Just composables sitting there in setup(), clean and unbothered, like they always belonged.
The Nuxt reactivity system and Anime.js finally having a conversation instead of passing notes through a middleman.
useAnimate() runs. The timeline breathes. The stagger cascades across your list items with the quiet confidence of someone who has never once had to explain themselves at a standup.
Is this a small thing? Technically yes.
Does it feel like the moment Gutenberg realized the press could do more than print indulgences?
Also yes.
Go look at nanimejs.netlify.app before your next onMounted reflex kicks in.
#NuxtJS #AnimeJS #WebAnimation #VueJS #Composables #FrontendDevelopment #JavaScript #WebDev
nanimeAnime.js Composables for Nuxt and Vue 3Anime.js v4 for Nuxt: SSR-safe, auto-imported composables and transitions for animation, scroll, drag and text
commit a0a9b7a