Nuxt 3 & GSAP: Why I Skip the Module and Go Manual In the Nuxt ecosystem, there is a module for almost everything. `@nuxtjs/gsap`? It exists. But just because a wrapper exists doesn’t mean you should always use it. If you’ve ever felt like a module was adding a layer of "magic" that made debugging harder rather than easier, this post is for you. Today, we’re going back to basics: installing GSAP via `npm` or `pnpm` and why it’s actually the superior way to handle animations in Nuxt 3. --- ## The "Module Fatigue" Realization Nuxt modules are fantastic for complex integrations (like Supabase or Auth). But for a library like GSAP, which is essentially a collection of JavaScript utilities, a module often just provides: 1. **Auto-imports:** Which take 2 seconds to set up manually. 2. **Plugin registration:** Which can be handled in a single file. 3. **Abstractions:** That might lag behind the actual GSAP version updates. By sticking to `npm install gsap`...
Comments
Post a Comment