react-native-brightness-newarch
Advanced tools
Easily control the screen brightness in your React Native app — compatible with both New and Old Architecture! ✨
Control the screen brightness without writing any native code.
npm install react-native-brightness-newarch
No extra linking needed for modern React Native versions.
Brightness values must be between 0 (minimum) and 1 (maximum).
import RNBrightness from "react-native-brightness-newarch";
// Set brightness to 50%
RNBrightness.setBrightnessLevel(0.5);
// Get current brightness
const current = await RNBrightness.getBrightnessLevel();
console.log(`Current brightness is: ${current}`);
⚠️ Out-of-range values are automatically clamped between 0 and 1.
This module automatically detects and supports both:
No configuration needed — it just works.
✅ Supports the New Architecture (TurboModules Ready)
✅ Fully Backward Compatible
✅ No Native Tweaks required (Plug & Play)
✅ Simple, Cross-Platform API
✅ Lightweight and Zero Dependencies
We welcome pull requests, issues, and ideas!
See the contributing guide for details.
FAQs
Brightness module for new architecture
We found that react-native-brightness-newarch demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A mini Shai-Hulud campaign compromised Red Hat Cloud Services npm packages to steal developer and CI/CD secrets during installation.
Research
/Security News
The North Korean malware loader hides in a Packagist-listed package and its GitHub branch to fetch and execute remote code in a likely Contagious Interview-style lure.
Security News
The Rust project is moving toward formal rules on LLM use in contributions after months of internal debate over maintainer burden, code quality, and contributor experience.