feat(studio): warn if studio is imported but not initialized

[0xTHAC0]

Summary

Addresses #21 — adds a helpful console.warn when @theatre/studio is imported but studio.initialize() is never called within 5 seconds.

What changed

• Extracted the initialization warning into a standalone InitWarning class (initWarning.ts) for testability
• Increased timeout from 100ms → 5s to give frameworks time to set up before warning
• Changed console.error → console.warn since this is a warning, not an error
• Timer is now properly cleared via clearTimeout() when initialize() is called (previously only checked a boolean flag)
• Added 5 unit tests covering:
  • Warning emits after timeout if studio not initialized
  • Warning does NOT emit if initialize() is called before timeout
  • Timer is cleared on initialize()
  • Late initialization warning emits if initialize() is called after timeout
  • initialize() is idempotent (returns false on second call)

Behavior

1. When @theatre/studio is imported, a 5-second timer starts
2. If studio.initialize() is called before the timer fires, the timer is cleared — no warning
3. If the timer fires without initialize() being called, a console.warn explains how to fix it
4. If initialize() is called after the warning, a second message notes the late initialization

Test plan

• yarn test — all existing tests pass (18 suites, 242 tests)
• 5 new tests pass covering both initialized and not-initialized paths

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
theatre-playground	Building	Preview	Aug 12, 2026 10:47am

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}