fix: support both new and old ColorSchemeName in RN

[Brentlok]

fix #323

Summary by CodeRabbit

• Bug Fixes
  • Improved compatibility with newer React Native releases to ensure consistent color-scheme handling and theme application across platforms (web and native).
  • Treats an "unspecified" system appearance as Light and uses a stable fallback on non-web platforms to avoid incorrect or missing theme states.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds React Native version awareness and maps RN's 'unspecified' color scheme to Light. Replaces use of undefined with an internal UNSPECIFIED_THEME when setting color schemes on non-web platforms and updates event/getter handling to avoid passing null/undefined to RN >= 0.82 APIs.

Changes

Cohort / File(s)	Summary
React Native 0.82+ compatibility packages/uniwind/src/core/config/config.common.ts	Introduces RN_VERSION (minor) and UNSPECIFIED_THEME; treats event.colorScheme === 'unspecified' as Light; getter maps 'unspecified' → Light; uses UNSPECIFIED_THEME instead of undefined when applying themes or handling SYSTEM_THEME on non-web platforms to avoid passing null to RN APIs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A little rabbit hops and sings,
RN versions, and new tiny things,
"unspecified" now whispers Light,
No more crashes in the night,
Hooray — the themes all sleep tight! 🥕✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main fix: adding support for the new 'unspecified' ColorSchemeName value in React Native 0.82+.
Linked Issues check	✅ Passed	The changes directly address issue #323 by handling the 'unspecified' color scheme value that causes crashes in RN 0.82+, preventing null parameter errors.
Out of Scope Changes check	✅ Passed	All changes are scoped to handling RN 0.82+ ColorSchemeName compatibility; no unrelated modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@packages/uniwind/src/core/config/config.common.ts`:
- Around line 7-8: The RN version check should safely read the numeric minor
version and compare it as an integer; change the logic around
RN_VERSION/UNSPECIFIED_THEME so it uses optional chaining to avoid
Platform.constants being undefined (e.g., read
Platform.constants?.reactNativeVersion?.minor ?? 0 into a RN_MINOR variable) and
compare RN_MINOR >= 82 (integer) to decide UNSPECIFIED_THEME ('unspecified' or
undefined). Update references to RN_VERSION and UNSPECIFIED_THEME in any
dependent code to use the new RN_MINOR-based check.

[niteshbalusu11]

Could you please make a release with this fix, since it is now merged.

[Brentlok]

Could you please make a release with this fix, since it is now merged.

Released in https://github.com/uni-stack/uniwind/releases/tag/v1.2.7