expo-permissions - npm Package Compare versions

Comparing version 6.0.0 to 7.0.0-rc.0

package.json

 {
   "name": "expo-permissions",
-  "version": "6.0.0",
+  "version": "7.0.0-rc.0",
   "description": "Allows you prompt for various permissions to access device sensors, personal data, etc.",
@@ -11,2 +11,3 @@ "main": "build/Permissions.js",
     "clean": "expo-module clean",
+    "lint": "expo-module lint",
     "test": "expo-module test",
@@ -24,3 +25,4 @@ "prepare": "expo-module prepare",
     "type": "git",
-    "url": "https://github.com/expo/expo.git"
+    "url": "https://github.com/expo/expo.git",
+    "directory": "packages/expo-permissions"
   },
@@ -41,5 +43,5 @@ "bugs": {
   "devDependencies": {
-    "expo-module-scripts": "^1.0.0"
+    "expo-module-scripts": "~1.1.1-rc.0"
   },
-  "gitHead": "9518929d6f2ba9cf8e0aae81d34cc1eb52f7093a"
+  "gitHead": "5d4fcf318390f59cecd1ae5d191afb15488a4447"
 }

README.md

@@ -10,6 +10,8 @@ # expo-permissions
 
-# Installation
+# Installation in managed Expo projects
 
-This package is pre-installed in [managed](https://docs.expo.io/versions/latest/introduction/managed-vs-bare/) Expo projects. You may skip the rest of the installation guide if this applies to you.
+For managed [managed](https://docs.expo.io/versions/latest/introduction/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects — it is likely to be included in an upcoming Expo SDK release.
 
+# Installation in bare React Native projects
+
 For bare React Native projects, this package is included in [`react-native-unimodules`](https://github.com/unimodules/react-native-unimodules). Please refer to those installation instructions to install this package.
@@ -16,0 +18,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

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

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

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

110845

increased by0.84%

Number of package files

58

increased by3.57%

Lines of code

571

increased by2.51%

Number of lines in readme file

21

increased by10.53%

Number of medium supply chain risk alerts

0

decreased by-100%

Worsened metrics

Number of low quality alerts

1

increased byInfinity%

No dependency changes