Fix useBreakPoint hook with provider pattern and improve media query handling #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR refactors the
useBreakPointhook to use a Context Provider pattern, improving error handling and ensuring proper initialization. It also fixes media query event listener management and updates tests accordingly.Key Changes
addEventListener/removeEventListener) and legacy (addListener/removeListener) APIsdefaultBreakPointContexttoundefinedto properly detect when the hook is used outside the provideruseMemofor media query arrays to prevent unnecessary re-renderswindow.matchMediauseBeakPoint→useBreakPointImplementation Details
if/elsestatements instead of early returns, ensuring both modern and legacy APIs are handled correctlytypeof defaultBreakPointContext | undefinedto enable runtime validationwindow.matchMediawith all required MediaQueryList methodshttps://claude.ai/code/session_01JEENKXTHsiUhVAfvJSAw6n