jetifier - npm Package Compare versions

Comparing version 1.6.0 to 1.6.1

CHANGELOG.md

 # Changelog
 
+## 1.6.1
+
+- docs(README): just docs changes but this gets them out on npmjs.com
+
 ## 1.6.0
@@ -4,0 +8,0 @@

package.json

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

README.md

@@ -82,3 +82,4 @@
 1. You have a dependency that does not allow overrides of compileSdk, so you can't set the compileSdk to 28 as AndroidX requires: <https://github.com/razorpay/react-native-razorpay/pull/201>. This can lead to errors in resource merger where styles reference unknown attributes. Open pull requests with the libraries that do this
-1. There used to be a big section on Windows troubleshooting because the original implementation was bash+sed, but [Yassine Fathi](m4tt72) contributed a node port and now it just runs. If it the new node version isn't working for you, `./node_modules/bin/jetify.sh` is still present in the archive and you can try it
+1. You are missing the 'node-pre-gyp' package - you may see this error `ENOENT: no such file or directory, stat 'node_modules/fsevents/node_modules/.bin/node-pre-gyp'` - if so try something like `npm -i --save-dev node-pre-gyp`, see #22
+1. A java file has import statements with wildcards that did not convert (`*`) - like `import android.support.v4.content.*`. This is a problem with the library, they should not use wildcards, they should use concrete imports. Open upstream issues with the library and use the excellent `patch-package` in the meantime to fix them until the library is updated. Example in [react-native-navigation](https://github.com/wix/react-native-navigation/pull/5218/files)
 
@@ -98,2 +99,3 @@ So far there has not been a case of `npx jetify` failing that wasn't based in an error in a library, so if you have a problem please examine the error and the dependency very closely and help the libraries with fixes.
 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
+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>
 1. Finally, not really related to AndroidX, but you may simply have to make some changes related to the new auto-linking. <https://github.com/react-native-community/cli/blob/master/docs/dependencies.md>
@@ -100,0 +102,0 @@

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

2739310

increased by0.03%

Number of lines in readme file

112

increased by1.82%

No dependency changes