Inspira UI: Animated Vue and Nuxt Components for Modern Interfaces

Filling the Animated Component Gap in Vue

Inspira UI exists to give Vue and Nuxt developers access to a category of components that was previously available mainly to React projects. Aceternity UI and Magic UI offer animated, physics-driven elements for React. The maintainer, Rahul Vashishtha, started Inspira UI after identifying the absence of similar options in the Vue ecosystem.

The project is not a standalone framework. It functions as a curated set of copy-paste components. You take what you need, drop it into your project, and adapt it. This architecture means there is no version constraint to manage at the dependency level, but it also means updates to individual components are not automatic. If the upstream component changes, you must manually update your copy.

The repository's README lists compatibility with both Vue and Nuxt as a stated design goal. The package.json confirms this: the project itself is built on Nuxt 4.3.1 and uses `@nuxt/ui` and `@vueuse/nuxt` as direct dependencies, making the Nuxt integration a first-class concern rather than an afterthought.

Repository Layout and How Components Are Distributed

The repository is structured as the documentation site for Inspira UI, not as a traditional npm library. The top-level directories include `app/`, `content/`, `registry/`, `modules/`, and `scripts/`. The `registry/` directory is where the component definitions live. The `scripts/` directory contains `build-registry.mts`, which compiles the registry before the site builds.

The package.json reveals the full build chain:

"build": "pnpm build:registry && nuxt build && pnpm build:copy"

The documentation site at inspira-ui.com serves as the distribution point. Developers browse the site, find the component they want, and copy its source. The project acknowledges its debt to `shadcn-vue`, which pioneered this distribution model in the Vue ecosystem.

Third-party dependencies in the project include `gsap` for animation, `motion-v`, `@splinetool/runtime` for 3D, `cobe` for globe visuals, and `ogl`. These are dependencies of the documentation site, which means individual components may or may not require them. The README does not specify which packages each component depends on; that information is on the documentation pages.

Running Inspira UI Locally as a Contributor

For contributors who want to work on the documentation site or add new components, the repository uses pnpm as the package manager. The package.json defines the standard development workflow:

pnpm dev

This starts the Nuxt development server. To build the full site, run:

pnpm build

This chains the registry build step with the Nuxt build. For running the registry build in isolation against a local server:

REGISTRY_URL=http://localhost:3000/r tsx ./scripts/build-registry.mts

The linting setup uses both `oxlint` and `eslint`. The Contribution Guide at `inspira-ui.com/getting-started/contribution` documents the full process for adding a component.

End users of the components do not need to clone this repository. The intended workflow is to visit the documentation site, find a component, and copy its code into your own project.

Feature Coverage and What the README Does Not Document

The README lists mobile optimization and Nuxt compatibility as explicit goals, and the acknowledgment of `@vueuse/nuxt` in the dependencies confirms SSR support is in scope. Beyond that, the README is brief. It points to the documentation site for usage examples, component configuration, and the full component catalog.

This matters practically. The README does not list which components are available, does not document whether components support TypeScript generics or slot APIs, and does not describe how animation configuration works. The README says the project offers a "configuration guide" at `/api/configuration` but does not reproduce that content.

For a Vue developer evaluating the project, the main gap is discoverability before visiting the site. You cannot determine from the repository alone whether a specific component you need exists, or what customization it supports.

Copy-Paste vs. an Installable Library: The Trade-Off

Inspira UI's main alternative in the React world is Aceternity UI itself, which follows the same copy-paste model. In the Vue world, `shadcn-vue` is the direct analogue: it ports `shadcn-ui` to Vue and uses the same distribution mechanism. The difference is scope. `shadcn-vue` focuses on accessible utility components following Radix's accessibility patterns; Inspira UI focuses on visual, animated components inspired by Aceternity UI and Magic UI.

A traditional Vue component library like Naive UI ships as an npm package with versioned releases. You install it once and updates arrive through `npm update`. The trade-off is that the library dictates its own design system, and overriding it requires understanding the library's token system.

Inspira UI's copy-paste model gives more control over individual component behavior. The cost is that keeping components current is a manual process. The project does not appear to publish a changelog per component, so knowing when an upstream change is worth backporting requires checking the GitHub repository directly.

License, Maintenance, and Community

Inspira UI is released under the MIT license, which permits commercial use, modification, distribution, and sublicensing without restriction.

The last push to the repository was on 2026-09-18. The project has no GitHub releases; components are distributed through the documentation site rather than versioned releases.

The project is community-driven in structure. The README credits contributions from both the maintainer and outside contributors, and links to a formal contribution guide. Sponsorship is available through GitHub Sponsors to support continued development.

Because there are no formal releases, there is no migration guide or deprecation policy documented in the README. Teams building on components from this project should treat each component as a snapshot and plan for manual updates when the source changes.

Editorial conclusion

Inspira UI suits Vue and Nuxt projects that need animated, visually polished components and where copying and adapting code directly is acceptable. Teams who want a conventional installable package with semantic versioning and a stable API surface should look elsewhere. Before committing to it, verify the specific components you need are documented at inspira-ui.com and that the project's copy-paste model fits your workflow, since there is no central package version to pin.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. unovue/inspira-ui on GitHub