Gathering detailed insights and metrics for @strawberry-code/react-native-set-version
Gathering detailed insights and metrics for @strawberry-code/react-native-set-version
Gathering detailed insights and metrics for @strawberry-code/react-native-set-version
Gathering detailed insights and metrics for @strawberry-code/react-native-set-version
A tool to set version in node and react-native projects
npm install @strawberry-code/react-native-set-version
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
22 Commits
7 Branches
1 Contributors
Updated on Apr 15, 2020
Latest Version
1.1.12
Package Id
@strawberry-code/react-native-set-version@1.1.12
Unpacked Size
24.58 kB
Size
5.69 kB
File Count
8
NPM Version
6.13.4
Node Version
12.15.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
This tool allows you to easily update the version of a React Native application. It will update the following files if found:
In order to use this package, your project version must comply with the format described on semver.org.
There are two ways to install react-native-set-version: globally and locally.
This is the recommended way to install react-native-set-version.
npm:
1npm install react-native-set-version --save-dev
yarn:
1yarn add react-native-set-version --dev
You can then use this command in your project directory to run react-native-set-version:
npm:
1$ npm run setVersion <version> 2-- or -- 3$ npm run set-version <version>
yarn:
1$ yarn setVersion <version> 2-- or -- 3$ yarn set-version <version>
This installation method allows you to use react-native-set-version in any project.
npm:
1npm install -g react-native-set-version
yarn:
1yarn global add react-native-set-version
You can then use this command in your project directory to run react-native-set-version:
1setVersion <version> 2-- or -- 3set-version <version>
When invoked, react-native-set-version will make the following changes to your project files:
The version attribute in package.json
will be updated with the specified version.
It will update the version name and the version code in both build.gradle
and AndroidManifest.xml
.
Version information should not be in the AndroidManifest.xml
since this information is overridden by build.gradle
.
See https://developer.android.com/studio/publish/versioning for further informations.
For that reason react-native-set-version
will only write in the AndroidManifest.xml
if android:versionCode
and/or android:versionName
are already in the file.
It will update the CFBundleShortVersionString and the CFBundleVersion in Info.plist
.
The Android version code represents your version number as an integer. This package uses the following format to generate this integer:
<MAJOR><MINOR ON 2 DIGITS><PATCH ON 2 DIGITS><BUILD NUMBER>
For instance, the first time you call set-version 3.1.4
, it will produce the version code 301041
.
If you call the command with the same version a second time, it will increment the build number, to produce 301042
.
This also applies if, for instance, you call set-version 3.1.4-rc.1
, and then set-version 3.1.4-rc.2
.
As for the CFBundleVersion
on iOS, it will produce a string in the format <MAJOR>.<MINOR>.<PATCH>.<BUILD NUMBER>
.
Example:
1$ yarn set-version 1.0.0-rc.1 2# Output 3# ... 4# Will set android version code to 100001 5# ... 6# Will set CFBundleVersion to 1.0.0.1 7$ yarn set-version 1.0.0-rc.2 8# Output 9# ... 10# Will set android version code to 100002 11# ... 12# Will set CFBundleVersion to 1.0.0.2 13$ yarn set-version 1.0.0 14# Output 15# ... 16# Will set android version code to 100003 17# ... 18# Will set CFBundleVersion to 1.0.0.3
This software uses the MIT license.
You must use the following style guide:
This project contains a linting config, you should setup eslint
into your IDE with .eslintrc.js
.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/22 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
41 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More