🚀 Discussion: React Wrapper for @interactive-video-labs/core

[taj54]

Hi everyone,

With the core interactive video library now available on npm:

npm i @interactive-video-labs/core

...let’s discuss building a thin React wrapper to streamline integration with React projects, while keeping things lightweight and close to the core API.

---

🧩 Why a Thin React Wrapper?

React is the go-to for modern UIs, and a minimal wrapper would:

• Allow easy embedding of interactive video in React apps
• Expose the core API via simple props and callbacks
• Handle mounting/unmounting and updates with minimal abstraction
• Let users access the underlying player instance if needed

---

🎯 Example Usage

A thin wrapper might look like this:

import { IVLabsPlayer } from "@interactive-video-labs/react";

<IVLabsPlayer
  src="/main.mp4"
  cues={cuePoints}
  onInteraction={handleInteraction}
  onResponse={handleResponse}
  onAnalytics={trackAnalytics}
/>

This component would directly leverage @interactive-video-labs/core, exposing its features through React props and events, without adding extra layers.

---

🛠️ Roadmap Thoughts

We plan to build this in a dedicated standalone repository (e.g., react-wrapper) outside the core package,
to keep concerns isolated and publishing clean.

Key goals:

• Keep the wrapper minimal and close to the core API
• Expose configuration and lifecycle hooks with React idioms
• Leave styling, controls, and UI decisions to the developer

---

🤝 Open Questions

• Are you using the core library in React already?
• Would a thin wrapper meet your needs, or do you want more abstraction?
• Interested in helping build or test this wrapper?

---

Let’s collaborate on a simple, effective React integration! Share your thoughts or interest below.

– Tajul (on behalf of Interactive Video Labs)

[taj54]

hey @Bmongo i have pushed the current changes fork it
anything relatate to react wrapper put here

[taj54]

hey @Bmongo is their any road block while developing the react wrapper ?

[Bmongo]

Sorry, I usually don't have time on weekdays, so I can only spend time on weekends to participate

[taj54]

If that's the case then fine .
If you struggle with someone feel free to ping me

[Bmongo]

I still think that the current project should use monorepo for project management, which is too fragmented when developing across multiple repositories.

[taj54]

We’re planning to write more wrappers around the core in the future. If we go with a monorepo, that’s going to create unnecessary coupling between these wrappers, slowing development and making maintenance harder.

Keeping them in separate repositories is a cautious, forward-looking decision — it preserves flexibility, ensures each wrapper can evolve at its own pace, and avoids the overhead that comes with a tightly bound monorepo structure.

[Bmongo]

monorepo allows each wrapper to be independent, and allows each wrapper to reference the core code, as well as better version updates in the future

[Bmongo]

I don't think it will lead to coupling