V4 Improvements

[nerdyman]

Perf

• Use CSS variables to apply current position
• Use CSS variables to apply bounds padding
• Remove resize observer - should be able to maintain position using CSS only
• Use pointer capture/release API instead of custom event binding in useEffect

Feat

• Make boundsPadding support any CSS unit
• Make keyboardIncrement support any CSS unit

Style

• Replace ESLint and Prettier with Biome
• Bump max line width
• Format all files

CI

• Get pipeline working with Biome
• Resolve Storybook/Playwright issues
• Resolve test report upload issues

Checks

• Add boundsPadding tests
• Ensure landscape and portrait functionality works as it did before
• Ensure keyboard increment functionality works as it did before

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
react-compare-slider	Error			Sep 26, 2025 7:16pm

[pkg-pr-new]

react-compare-slider-example

npm i https://pkg.pr.new/nerdyman/react-compare-slider@170

commit: 9b50deb

[Copilot]

Pull Request Overview

This PR refactors slider positioning to rely on CSS variables, removes the resize observer, and extends boundsPadding to accept arbitrary CSS units.

• Replaced manual DOM clipping and resize observer with a CSS variable–based approach (currentPosition and boundsPadding).
• Updated the boundsPadding prop from number to string, enabling any CSS unit.
• Simplified event handling and merged imperative position updates into a single setPosition callback.

Reviewed Changes

Copilot reviewed 25 out of 25 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
lib/src/utils.ts	Consolidated imports; removed useResizeObserver; adjusted hooks for undefined targets.
lib/src/types.ts	Changed several interfaces to type; updated boundsPadding to string.
lib/src/consts.ts	Added ReactCompareSliderCssVars for CSS variable names.
lib/src/ReactCompareSlider.tsx	Rewrote position logic to use CSS vars; removed resize observer; centralized setPosition.
lib/src/Container.tsx	Updated clipping to use CSS vars; removed explicit position prop on handle.
lib/src/useReactCompareSliderRef.ts	Minor formatting change to console.warn.
docs/**/*	Adjusted stories and README to reflect boundsPadding: string; cleaned up formatting.
.vscode/settings.json	Increased ruler width to 110.
.prettierrc.js, .editorconfig	Updated line length settings to 110.
.github/workflows/publish-preview.yml	Bumped actions versions and simplified install command.

Comments suppressed due to low confidence (3)

lib/src/types.ts:50

• The keyboardIncrement prop still accepts only number according to the type definitions, but the implementation now supports string units; update its type to string | number and adjust documentation accordingly.

  boundsPadding?: string;

README.md:78

• Update the description for boundsPadding to reflect that it accepts any CSS unit (e.g., px, %, rem), not just pixels.

| [`boundsPadding`](https://react-compare-slider.vercel.app/?path=/story/demos--bounds-padding)                   | `string`                     |   | `0%`           | Padding to limit the slideable bounds in pixels on the X-axis (landscape) or Y-axis (portrait).

lib/src/Container.tsx:95

• Removing the default aria-valuenow attribute could cause a missing initial slider value in assistive technologies. Ensure an initial aria-valuenow is set, for example by passing the initial position prop or adding a default attribute.

        aria-valuemax={100}

[Copilot]

Parsing keyboardIncrement strings only via parseFloat treats any unit as a percentage, so passing pixel values (e.g. '20px') will not convert correctly. Consider detecting unit suffixes ('%', 'px', etc.) and converting accordingly to percent or pixel-based increments.

Suggested change

	? parseFloat(keyboardIncrement)
	? (() => {
	const match = keyboardIncrement.match(/^([\d.]+)(px|%)?$/);
	if (!match) {
	console.warn('Invalid keyboardIncrement value:', keyboardIncrement);
	return 0; // Default to 0 if the value is invalid
	}
	const [, value, unit] = match;
	const numericValue = parseFloat(value);
	if (unit === 'px') {
	return (numericValue / width) * 100; // Convert pixels to percentage
	}
	return numericValue; // Assume percentage if unit is '%' or undefined
	})()

[Copilot]

Pull Request Overview

Copilot reviewed 47 out of 48 changed files in this pull request and generated 3 comments.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}