
Product
Introducing Tier 1 Reachability: Precision CVE Triage for Enterprise Teams
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
react-native-simboot
Advanced tools
A script to spin up any simulator or device with your selected configuration.
Tired from searching an UUID or deviceID after adding a new simulator? A colleague wants to see the prototype on his own phone just "real quick"? Confused about the different build configurations in your project?
This script will speed up deploying your ReactNative app to a simulator or a device for testing.
It automatically searches for any available simulator or device. (iOS only at the moment) The script will pick up any available build configuration from Xcode (iOS) or the productFlavor and buildType variants from build.gradle (Android) and let you choose which one you want to run your app with.
After the prompt, the script will run the react-native run-<os>
command and start the app on the selected device.
yarn:
yarn add -D react-native-simboot
npm:
npm i -D react-native-simboot
Simply run in the root folder of your RN project:
npx react-native simboot --ios # run ios build
npx react-native simboot --android # run android build
If you are developing react-native apps on your machine, you should have the following tools already installed:
Usually the project files are located in the ios and android folders. If you have a different structure, you can specify the path to the Xcode project and the Gradle project with these flags.
If you have set the locations in react-native.config.js
, they should be automatically detected.
--ios-xcodeproj-path [string] # specify custom xcode project path
--android-gradle-path [string] # specify custom build.gradle path
Flag | Info | OS |
---|---|---|
--uuid | From user selection | iOS |
--configuration | From user selection | iOS |
--variant | Composed from productFlavor & buildType selection | android |
--appId | Taken from defaultConfig in build.gradle. Overwritten if value set in choosen productFlavor | android |
--deviceId | From user selection ⚠️ only supported with RN 0.72.0-rc.0 or react-native-cli 11.0.0 or higher (see Issue). Device selection for android not availabe if lower cli version detected | android |
You can configure the script by adding a simboot.config.js
file to the root of your project.
Value | Type | Explanation |
---|---|---|
verbose | boolean | get detailed output |
dryRun | boolean | don't run any build after selection |
customScriptPhase | (config: SelectedConfig) => void | run custom script after selection but before react-native build (e.g to set env). config contains the selected configuration |
Depending on the operating system selected, the customScriptPhase
function will be called with config
containing the following values:
interface SelectedConfig {
ios: {
configuration?: string
device?: {
name: string
udid: string
}
}
}
interface SelectedConfig {
android: {
buildType?: string
productFlavor?: string
}
}
🏃 Running react-native-simboot
🍏 Running iOS script
👀 Collecting build information
✔ Pick configuration:
❯ Debug
Release
Stage
✔ Pick a device:
iPad Pro (12.9-inch) (6th generation) - iOS 16.2
iPad Pro (9.7-inch) - iOS 15.0
iPad mini (6th generation) - iOS 15.0
iPad mini (6th generation) - iOS 16.2
❯ iPhone 13 - iOS 15.0
iPhone 13 Pro - iOS 15.0
iPhone 13 Pro Max - iOS 15.0
iPhone 13 mini - iOS 15.0
↓ iPhone 14 - iOS 16.2
🚀 ReactNative build finished successfully
FAQs
A script to spin up any simulator or device with your selected configuration.
The npm package react-native-simboot receives a total of 8 weekly downloads. As such, react-native-simboot popularity was classified as not popular.
We found that react-native-simboot demonstrated a not healthy version release cadence and project activity because the last version was released 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.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.