New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More

react-native-code-push

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

react-native-code-push - npm Package Compare versions

Comparing version 6.0.0 to 6.1.0

@@ -40,9 +40,9 @@ # Contributing

Then, make sure you have installed `gulp`.
Then, make sure you have installed `react-native-cli`.
```
npm install -g gulp
npm install -g react-native-cli
```
To run Android tests, make sure you have `sdk\tools` and `sdk\platform-tools` in your PATH.
To run Android tests, make sure you have `sdk\tools`, `sdk\emulator` and `sdk\platform-tools` in your PATH.

@@ -66,20 +66,18 @@ To run iOS tests, make sure you've installed CocoaPods and have `.gem/bin` in your PATH.

If an Android emulator is not running, it attempts to boot an Android emulator named `emulator`. You can specify an emulator by adding `--androidemu yourEmulatorNameHere` as a command line option to the gulp task.
If an Android emulator is not running, it attempts to boot the latest Android emulator. You can specify an emulator by adding env variable `ANDROID_EMU=yourEmulatorNameHere` to the npm command. For example: `ANDROID_EMU=yourEmulatorNameHere npm run test:android`.
If an iOS simulator is not running, it attempts to boot the latest iOS iPhone simulator. You can specify a simulator by adding `--iosemu yourSimulatorNameHere` as a command line option to the gulp task.
If an iOS simulator is not running, it attempts to boot the latest iOS iPhone simulator. You can specify a simulator by adding env variable `IOS_EMU=yourSimulatorNameHere` to the npm command. For example: `IOS_EMU="iPhone 8 (0567DFF8-329E-41A3-BD6D-E48E9DD5EF39)" npm run test:ios`.
If all the required emulators are not running and the tests fail to boot them, the tests will fail.
If you would like the tests to always restart the necessary emulators (killing them if they are currently running), add a `--clean` flag to the command.
If you would like the tests to always restart the necessary emulators (killing them if they are currently running), setup a env variable `CLEAN=true` to the command. For example: `CLEAN=true npm run test`.
The desired unit tests are then run.
If you would like to skip building, add a `-fast` to the end of the command you'd like to run. For example, `gulp test-ios` becomes `gulp test-ios-fast`.
If you would like to skip building, add a `:fast` in the command you'd like to run. For example, `npm run test:ios` becomes `npm run test:fast:ios` or `npm run test:android` becomes `npm run test:fast:android`.
There is a both a full unit test suite and a "core" set of unit tests that you may run. If you would like to run only the core tests, add a `--core` flag to the command.
There is a both a full unit test suite and a "core" set of unit tests that you may run. If you would like to run only the core tests, setup a env variable `CORE=true` to the command. For example: `CORE=true npm run test:android`.
If you would like to pull the plugin from NPM rather than running the tests on the local version, add a `--npm` flag to the command.
If you would like to pull the plugin from NPM rather than running the tests on the local version, setup a env variable `NPM=true` to the command. For example: `NPM=true npm run test:ios`.
If you add a `--report` flag to the command, the mocha reporter outputs individual results files for each platform. These are `./test_android.xml`, `./test-ios-ui.xml`, and `./test-ios-wk.xml`.
#### Default

@@ -89,3 +87,3 @@

```
gulp test
npm run test
```

@@ -97,3 +95,3 @@

```
gulp test-ios
npm run test:ios
```

@@ -105,3 +103,3 @@

```
gulp test-android
npm run test:android
```

@@ -118,3 +116,3 @@

```
gulp test-android --core
CORE=true npm run test:android
```

@@ -124,3 +122,3 @@

```
gulp test-ios --npm
NPM=true npm run test:ios
```

@@ -130,3 +128,3 @@

```
gulp test-fast
npm run test:fast
```

@@ -136,3 +134,3 @@

```
gulp test-ios --clean
CLEAN=true npm run test:ios
```

@@ -142,5 +140,5 @@

```
gulp test-android --core --npm
NPM=true CORE=true npm run test:android
```
...and so on!

@@ -419,3 +419,3 @@ ## Android Setup

Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/Microsoft/code-push/tree/master/cli#code-signing). In order to use Public Key for Code Signing you need to do following steps:
Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/Microsoft/code-push/tree/v3.0.1/cli#code-signing). In order to use Public Key for Code Signing you need to do following steps:

@@ -422,0 +422,0 @@ Add `CodePushPublicKey` string item to `/path_to_your_app/android/app/src/main/res/values/strings.xml`. It may looks like this:

@@ -262,3 +262,3 @@ ## iOS Setup

Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/Microsoft/code-push/tree/master/cli#code-signing).
Starting with CLI version **2.1.0** you can self sign bundles during release and verify its signature before installation of update. For more info about Code Signing please refer to [relevant code-push documentation section](https://github.com/Microsoft/code-push/tree/v3.0.1/cli#code-signing).

@@ -265,0 +265,0 @@ In order to configure Public Key for bundle verification you need to add record in `Info.plist` with name `CodePushPublicKey` and string value of public key content. Example:

{
"name": "react-native-code-push",
"version": "6.0.0",
"version": "6.1.0",
"description": "React Native plugin for the CodePush service",

@@ -15,2 +15,20 @@ "main": "CodePush.js",

"license": "MIT",
"scripts": {
"clean": "shx rm -rf bin",
"setup": "npm install --quiet --no-progress",
"prebuild:tests": "npm run clean && npm run tslint",
"build:tests": "tsc",
"test": "npm run build:tests && npm run test:setup && npm run test:fast",
"test:android": "npm run build:tests && npm run test:setup:android && npm run test:fast:android",
"test:ios": "npm run build:tests && npm run test:setup:ios && npm run test:fast:ios",
"test:setup": "mocha --recursive bin/test --android --ios --setup",
"test:setup:android": "mocha --recursive bin/test --android --setup",
"test:setup:ios": "mocha --recursive bin/test --ios --setup",
"test:fast": "mocha --recursive bin/test --android --ios",
"test:fast:android": "mocha --recursive bin/test --android",
"test:fast:ios": "mocha --recursive bin/test --ios",
"test:debugger:android": "mocha --recursive --inspect-brk=0.0.0.0 bin/test --android",
"test:debugger:ios": "mocha --recursive --inspect-brk=0.0.0.0 bin/test --ios",
"tslint": "tslint -c tslint.json test/**/*.ts"
},
"repository": {

@@ -21,11 +39,16 @@ "type": "git",

"dependencies": {
"code-push": "^3.0.1",
"code-push": "^3.1.0",
"glob": "^5.0.15",
"hoist-non-react-statics": "^2.3.1",
"inquirer": "^1.1.2",
"inquirer": "^7.0.3",
"plist": "3.0.1",
"semver": "^5.6.0",
"semver": "^7.1.1",
"xcode": "1.0.0"
},
"devDependencies": {
"@types/assert": "^1.4.3",
"@types/mkdirp": "^0.5.2",
"@types/mocha": "^5.2.7",
"@types/node": "^13.1.8",
"@types/q": "^1.5.2",
"archiver": "latest",

@@ -36,10 +59,10 @@ "body-parser": "latest",

"express": "latest",
"gulp-insert": "latest",
"gulp-tslint": "latest",
"gulp-typescript": "^5.0.1",
"mkdirp": "latest",
"mocha": "^7.0.0",
"q": "^1.5.1",
"run-sequence": "latest",
"tslint": "^5.18.0",
"typescript": "^2.9.2"
"shx": "^0.3.2",
"slash": "^3.0.0",
"tslint": "^5.20.1",
"typescript": "^3.7.5"
},

@@ -46,0 +69,0 @@ "rnpm": {

@@ -255,3 +255,3 @@ UPDATE: Over the next few months, we will be working on a new version of CodePush that will address some of the most common performance issues our customers are facing. This updated version will allow a better experience, our team to better support CodePush moving forward and have a faster development cycle for new features.

For more details about how the `release-react` command works, as well as the various parameters it exposes, refer to the [CLI docs](https://github.com/Microsoft/code-push/tree/master/cli#releasing-updates-react-native). Additionally, if you would prefer to handle running the `react-native bundle` command yourself, and therefore, want an even more flexible solution than `release-react`, refer to the [`release` command](https://github.com/Microsoft/code-push/tree/master/cli#releasing-updates-general) for more details.
For more details about how the `release-react` command works, as well as the various parameters it exposes, refer to the [CLI docs](https://github.com/Microsoft/code-push/tree/v3.0.1/cli#releasing-updates-react-native). Additionally, if you would prefer to handle running the `react-native bundle` command yourself, and therefore, want an even more flexible solution than `release-react`, refer to the [`release` command](https://github.com/Microsoft/code-push/tree/v3.0.1/cli#releasing-updates-general) for more details.

@@ -258,0 +258,0 @@ If you run into any issues, or have any questions/comments/feedback, you can ping us within the [#code-push](https://discord.gg/0ZcbPKXt5bWxFdFu) channel on Reactiflux, [e-mail us](mailto:codepushfeed@microsoft.com) and/or check out the [troubleshooting](#debugging--troubleshooting) details below.