@next/react-refresh-utils - npm Package Compare versions

Comparing version 0.0.0 to 9.3.6-canary.4

package.json

 {
   "name": "@next/react-refresh-utils",
-  "version": "0.0.0",
-  "description": "",
-  "main": "index.js",
+  "version": "9.3.6-canary.4",
+  "description": "An experimental package providing utilities for React Refresh.",
+  "repository": {
+    "url": "zeit/next.js",
+    "directory": "packages/react-refresh-utils"
+  },
+  "files": [
+    "internal/*.d.ts",
+    "internal/*.js",
+    "*.d.ts",
+    "*.js"
+  ],
+  "author": "Joe Haddad <[e-mail]>",
+  "license": "MIT",
   "scripts": {
-    "test": "echo \"Error: no test specified\" && exit 1"
+    "prepublish": "tsc -d -p tsconfig.json",
+    "build": "tsc -d -w -p tsconfig.json"
   },
-  "keywords": [],
-  "author": "",
-  "license": "MIT"
+  "peerDependencies": {
+    "react-refresh": "0.8.1",
+    "webpack": "^4"
+  },
+  "devDependencies": {
+    "react-refresh": "0.8.1",
+    "webpack": "4.42.1"
+  },
+  "gitHead": "86236bc76bcfc69b4e704f06be5b29cda3c1908c"
 }

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

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

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

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

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

No README

Quality

Package does not have a README. This may indicate a failed publish or a low quality package.

Found 1 instance in 1 package

No contributors or author data

Maintenance

Package does not specify a list of contributors or an author in package.json.

Found 1 instance in 1 package

No repository

Supply chain risk

Package does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.

Found 1 instance in 1 package

No tests

Quality

Package does not have any tests. This is a strong signal of a poorly maintained or low quality package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

17321

increased by7147.28%

Number of package files

13

increased by1200%

Lines of code

340

increased byInfinity%

Number of low maintenance alerts

1

decreased by-50%

Number of low quality alerts

2

decreased by-33.33%

Number of medium quality alerts

0

decreased by-100%

Number of lines in readme file

18

increased byInfinity%

Worsened metrics

Dependency count

2

increased byInfinity%

Dev dependency count

2

increased byInfinity%

Number of medium supply chain risk alerts

2

increased by100%

No dependency changes