docs: upstream issues fixed in @cyberlz/react-date-range 1.0.0

[sokaluis]

Summary

@cyberlz/react-date-range@1.0.0 is now published as the maintained fork of the archived upstream hypeserver/react-date-range package.

The upstream repository is archived/read-only, so we cannot reliably comment on or create upstream issues. This issue serves as the public index of upstream issues and PRs we worked through, resolved, verified, or explicitly deferred in this fork.

Stable release references

• npm: https://www.npmjs.com/package/@cyberlz/react-date-range/v/1.0.0
• GitHub Release: https://github.com/sokaluis/react-date-range/releases/tag/v1.0.0
• Migration guide: https://github.com/sokaluis/react-date-range/blob/main/docs/migration-from-upstream.md
• Upstream issue tracker: https://github.com/sokaluis/react-date-range/blob/main/docs/upstream-issue-tracker.md

Upstream issues/PRs resolved in this fork

Upstream	Topic	Fork status
hypeserver/react-date-range#661	React 19 peer dependency / compatibility	Resolved with first-party types and React 19 TS spike
hypeserver/react-date-range#662	JSX component type issues with React 19	Resolved with first-party types
hypeserver/react-date-range#604	Earlier JSX/component type issue	Resolved with first-party types
hypeserver/react-date-range#260	TypeScript support request	Resolved with bundled src/index.d.ts
hypeserver/react-date-range#439	TypeScript type improvements	Resolved with first-party types based on community shape
hypeserver/react-date-range#513	TypeScript strict mode issues	Resolved/validated with React 18 and React 19 TS fixtures
hypeserver/react-date-range#654	date-fns v4 guard / compatibility	Resolved by narrowing peer dependency to date-fns@^3
hypeserver/react-date-range#665	Color ReferenceError / TDZ fallback	Resolved in fork
hypeserver/react-date-range#508	focusedRange end-date handling	Verified correct and regression-tested
hypeserver/react-date-range#577	Scroll issues in React 18 StrictMode	Resolved with timer cleanup and ReactList cache refresh
hypeserver/react-date-range#653	Infinite scroll in StrictMode	Resolved with the same StrictMode scroll fix
hypeserver/react-date-range#539	DateInput min/max typed validation	Resolved with DateInput validation work
hypeserver/react-date-range#658	DateRange.updatePreview temporal dead zone	Resolved and regression-locked
hypeserver/react-date-range#664	date-fns addYears is not a function in CRA/Webpack	Resolved by named date-fns imports and peer guard
hypeserver/react-date-range#663	date-fns import changes / CRA smoke	Resolved with same root fix as #664
hypeserver/react-date-range#607	disabledDates crash on non-array	Resolved with Calendar-boundary array guard

Verified / no extra code change needed

Upstream	Topic	Fork status
hypeserver/react-date-range#649	date-fns v3/v4 compatibility	Covered by peer dependency guard and verified

Tracked but not part of 1.0.0

Upstream	Topic	Fork status
hypeserver/react-date-range#373	Accessibility / keyboard navigation	Future accessibility pass
hypeserver/react-date-range#415	Accessibility improvements	Future accessibility pass
hypeserver/react-date-range#416	ARIA roles and labels	Future accessibility pass
hypeserver/react-date-range#669	RTL styles	Future visual proposal, not committed roadmap
hypeserver/react-date-range#495	Cross-month range selection UX	Future UX proposal
hypeserver/react-date-range#470	Time picker support	Out of scope for compatibility-maintenance fork
hypeserver/react-date-range#590	Maintenance / takeover discussion	Documented: this fork is the active maintenance effort

Notes for adopters

• Public API target: drop-in public API compatibility with upstream react-date-range@2.0.1 plus corrected behavior.
• Recommended install: npm install @cyberlz/react-date-range.
• If migrating from upstream, start with docs/migration-from-upstream.md.