jetifier - npm Package Compare versions

Comparing version 1.2.0 to 1.3.0

package.json

 {
   "name": "jetifier",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "jetifier from Android Studio, in npm package format",
@@ -5,0 +5,0 @@ "main": "index.js",

README.md

@@ -21,3 +21,3 @@ # jetifier
 
-If there was a way to take your react-native dependencies and convert them, then you could convert your app and use AndroidX dependencies. 
+If there was a way to take your react-native dependencies and convert them, then you could convert your app and use AndroidX dependencies.
 
@@ -28,6 +28,5 @@ **There is a way**.
 1. `npm install --save-dev jetifier` (or use yarn, but install it locally in your project, not globally)
-1. `npx jetify`
-1. Get a cup of coffee, it takes a while. Performance improvements can come later.
+1. `npx jetify` or `npx jetify -w=1` (to specify the number of parallel workers)
 1. `npx react-native run-android` (this should compile and work)
-1. If it works, you should hook an `npx jetify` run in the postinstall target of your package.json so you don't forget to run it after installing or updating packages. There will be performance improvements soon (I think) which will make this less painful
+1. If it works, you should hook an `npx jetify` run in the postinstall target of your package.json so you don't forget to run it after installing or updating packages
 
@@ -65,4 +64,8 @@ Please note that any time you install a new dependency, or reinstall node modules, you will need to run `npx jetify` again.
 
+### Performance (how to set workers parameter)
+
+In testing, it appeared that performance improved up to the number of virtual cores on a system, and then was flat but did not degrade after that no matter how many extra workers there were. So the default of 20 should result in maximum performance on even powerful systems, but smaller CI virtual machines should be fine as well. Your mileage may vary.
+
 ## Contributing
 
 Please feel free to pull requests or log issues, especially to update versions if I somehow fail to notice an update. Thanks!

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

2725372

increased by0.02%

Number of lines in readme file

69

increased by4.55%

No dependency changes