@remotion/drag-and-drop: Add Install in Studio interface

[JonnyBurger]

Summary

• add a shared installInStudio() transport to @remotion/drag-and-drop
• expose typed Studio target and install result metadata
• refactor the Elements gallery to use the shared interface
• cover target selection and install failures with tests

Testing

• bun run build
• bun run stylecheck
• bun test packages/drag-and-drop/src/test

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Jul 24, 2026 12:03pm
remotion	Ready	Preview, Comment	Jul 24, 2026 12:03pm

[pullfrog]

Reviewed changes — extracts the “Install in Studio” logic from the docs ElementPage into @remotion/drag-and-drop as a shared installInStudio() transport, exposes typed StudioInstallTarget and InstallInStudioResult, and refactors the Elements gallery caller.

• New installInStudio() function with dependency injection (fetchFn, now, ports) so it can be tested without making real network calls.
• New StudioInstallTarget and InstallInStudioResult types exported from @remotion/drag-and-drop, with the origin field promoted into the target type (previously assembled ad-hoc by the caller).
• Runtime response validation via isStudioInstallTarget() and isRecord() — the old code used a bare as ElementInstallTarget cast.
• Simplified ElementPage.tsx caller from ~70 lines of inline probing/fetching/error-handling logic to a single DragAndDropInternals.installInStudio(dragData) call.
• 3 tests covering most-recently-focused target selection, no-available-studio error, and rejected-install error propagation.

`@remotion/drag-and-drop`: Add Install in Studio interface

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}