This looks useful, especially because it follows the shadcn/ui copy-paste model instead of forcing a heavy setup.

The strongest part is the "zero config, one command setup" angle. For video components, setup friction is usually the thing that stops people from trying a library.

One thing I'd be curious about: are the components mostly presentation-focused, or do they also handle interactive video states like timeline progress, playback controls, hover previews, captions, and loading/error states?

Either way, the open-source + shadcn-compatible approach makes this easy to test in existing Next.js projects.