jetifier - npm Package Compare versions
Comparing version 1.6.3 to 1.6.4
| # Changelog | ||
| ## 1.6.4 | ||
| - fix: link jetify to jetifier name, `npx jetifier` works (thanks @salakar for the assist) | ||
| ## 1.6.3 | ||
@@ -4,0 +7,0 @@ - fix: avoid substring/superstring shadowing in regex (#32) thanks @mysport12! |
| { | ||
| "name": "jetifier", | ||
| "version": "1.6.3", | ||
| "version": "1.6.4", | ||
| "description": "jetifier from Android Studio, in npm package format", | ||
@@ -8,3 +8,4 @@ "main": "index.js", | ||
| "jetifier-standalone": "./bin/jetifier-standalone", | ||
| "jetify": "./bin/jetify" | ||
| "jetify": "./bin/jetify", | ||
| "jetifier": "./bin/jetify" | ||
| }, | ||
@@ -11,0 +12,0 @@ "scripts": { |
@@ -95,3 +95,3 @@ [](http://badge.fury.io/js/jetifier) | ||
| 1. Dependency version overrides. In your library, all of your dependencies and your SDK versions should have version overrides. These offer your users flexibility to pin the versions to pre-AndroidX or AndroidX versions. Example: <https://github.com/razorpay/react-native-razorpay/pull/201> and showing ability to be very specific: <https://github.com/react-native-community/react-native-camera/blob/master/android/build.gradle#L78> | ||
| 1. AppCompat library _name_ overrides - this may seem odd, but if you depend on the appcompat library itself, the whole name may need to be overridden to work correctly on RN0.60. Here is an example: <https://github.com/react-native-community/react-native-maps/commit/0c76619e8b4d591265348beb83f315ad05311670> | ||
| 1. AppCompat library _name_ overrides - this may seem odd, but if you depend on the appcompat (or similar) library itself, the whole name may need to be overridden to work correctly on RN0.60. Here is an example: <https://github.com/react-native-community/react-native-device-info/commit/d448d872906335813d53a7e8f8dc7860ae160c40> | ||
| 1. There may be unexpected problems like one of your dependencies is doing something wrong, but it's not really your fault - bottomsheet had that problem <https://github.com/acaziasoftcom/react-native-bottomsheet/pull/23> - keep an open mind about the fixes and there is probably something you can do without giving up on forwards and backwards compatibility during the transition | ||
@@ -98,0 +98,0 @@ 1. Do not use wildcard imports of support library classes, but you don't need to convert to AndroidX to fix them. Just make a patch release with the concrete imports like react-native-navigation - <https://github.com/wix/react-native-navigation/pull/5218/files> |
New alerts
License Policy Violation
LicenseThis 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
LicenseThis 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
- increased by0.01%
2739973