You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 21, 2026. It is now read-only.
Repository navigation
refactor(react)!: separate slider render and motion state - #2327
Each entry is independently bundled, minified, and brotli-compressed. Initial size includes its static import graph; lazy dynamic chunks are reported separately.
Entries are not additive because their dependency graphs overlap. Preset rows represent realistic combined bundles.
Changes of 300 B or less across initial, lazy, and total size are collapsed, not discarded.
Run pnpm size locally to check current initial sizes.
Closing in its current form after re-reviewing against current main. The semantic/motion split is still the right direction and useSliderMotion is a reasonable public hook, but this branch cannot be rebased safely:
alignState/getAlignmentSizes reimplement adjustForAlignment from core in React while HTML keeps the core path, which duplicates geometry math across packages.
Renaming input → motion and changing computeState break the documented useSlider surface with no RFC.
Plan: once the #2325 utility layer lands, reopen as two PRs on main. First a non-breaking PR for React-owned fill/buffer CSS variables and edge-only geometry observation, then useSliderMotion with a deprecated input alias and a short RFC for the computeState change, with edge-alignment measurement moved into SliderApi so core stays the single owner. Refs #1679.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Refs #1679
Depends on #2325.
Summary
useSliderMotion()for pointer-driven custom content while keeping ordinary render, className, and style callbacks stable.--media-slider-pointer.Breaking changes
useSlider()returnsmotioninstead ofinput.computeStatereceives discreteSliderInteractionStaterather than the full input object.SliderRenderStateand omits high-frequency pointer motion.useSliderMotion()inside a slider root.Verification