react-devtools - npm Package Compare versions

Comparing version 3.1.0 to 3.2.0

package.json

 {
   "name": "react-devtools",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Use react-devtools outside of the browser",
@@ -29,5 +29,5 @@ "repository": {
     "minimist": "^1.2.0",
-    "react-devtools-core": "^3.1.0",
+    "react-devtools-core": "^3.2.0",
     "update-notifier": "^2.1.0"
   }
 }

README.md

@@ -13,3 +13,11 @@ # `react-devtools`
 
+with yarn:
+
 ```
+yarn global add react-devtools
+```
+
+or with npm:
+
+```
 npm install -g react-devtools
@@ -59,3 +67,10 @@ ```
 
+with yarn:
 ```
+yarn global add react-devtools
+```
+
+or with npm:
+
+```
 npm install -g react-devtools
@@ -82,3 +97,3 @@ ```
 
->Note: if you prefer to avoid global installations, you can add `react-devtools` as a project dependency. With Yarn, you can run `yarn add --dev react-devtools`, and then run `yarn react-devtools` from your project folder to open the DevTools. With npm, you can run `npm install --save-dev react-devtools`, add `"react-devtools": "react-devtools"` to the `scripts` section in your `package.json`, and then run `npm run react-devtools` from your project folder to open the DevTools. 
+>Note: if you prefer to avoid global installations, you can add `react-devtools` as a project dependency. With Yarn, you can run `yarn add --dev react-devtools`, and then run `yarn react-devtools` from your project folder to open the DevTools. With npm, you can run `npm install --save-dev react-devtools`, add `"react-devtools": "react-devtools"` to the `scripts` section in your `package.json`, and then run `npm run react-devtools` from your project folder to open the DevTools.
 
@@ -94,5 +109,5 @@ >If you install `react-devtools` as a project dependency, you may also replace the `<script>` suggested above with a JavaScript import (`import 'react-devtools'`). It is important that this import comes before any other imports in your app (especially before `react-dom`). Make sure to remove the import before deploying to production, as it carries a large DevTools client with it. If you use Webpack and have control over its configuration, you could alternatively add `'react-devtools'` as the first item in the `entry` array of the development-only configuration, and then you wouldn’t need to deal either with `<script>` tags or `import` statements.
 
-* Run `npm run backend:watch` and `npm run standalone:watch` in `../react-devtools-core`
-* Run `npm start` in this folder
+* Run `yarn run backend:watch` and `yarn run standalone:watch` in `../react-devtools-core`
+* Run `yarn start` in this folder
 * Refresh the app after it has recompiled on change
 * For React Native, copy `react-devtools-core` to its `node_modules` to test your changes

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

Native code

Supply chain risk

Contains native code (e.g., compiled binaries or shared libraries). Including native code can obscure malicious behavior.

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

22577

increased by38.49%

Number of package files

8

increased by14.29%

Number of lines in readme file

110

increased by15.79%

Worsened metrics

Number of medium supply chain risk alerts

1

increased byInfinity%

Dependency changes

• Updatedreact-devtools-core@^3.2.0