umami/packages/dials/src
Sajid Mehmood 23a3c6cf6b Fix dials HMR by using window-based singleton
The static class property singleton pattern doesn't survive HMR
when module boundaries get crossed. New dials would register with
a fresh registry instance while DialsOverlay stayed subscribed to
the old one.

Fix: Store the singleton on `window.__NITESHIFT_DIALS_REGISTRY__`
so it persists across module re-evaluations during hot reload.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-26 11:46:02 -05:00
..
__tests__ Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
components Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
controls Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
hooks Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
utils Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
index.ts Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
registry.ts Fix dials HMR by using window-based singleton 2025-11-26 11:46:02 -05:00
styles.css Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00
types.ts Add Niteshift Dials SDK for runtime design prototyping 2025-11-26 11:46:02 -05:00