@verdaccio/file-locking - npm Package Compare versions

Comparing version 1.0.2 to 1.0.3

CHANGELOG.md

@@ -5,2 +5,12 @@ # Change Log
 
+<a name="1.0.3"></a>
+## [1.0.3](https://github.com/verdaccio/file-locking/compare/v1.0.2...v1.0.3) (2019-06-22)
+
+
+### Bug Fixes
+
+* update build script and remove source map ([ec3db50](https://github.com/verdaccio/file-locking/commit/ec3db50))
+
+
+
 <a name="1.0.2"></a>
@@ -7,0 +17,0 @@ ## [1.0.2](https://github.com/verdaccio/file-locking/compare/v1.0.1...v1.0.2) (2019-06-15)

package.json

 {
   "name": "@verdaccio/file-locking",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "library that handle file locking",
@@ -48,3 +48,5 @@ "main": "lib/index.js",
     "type-check:watch": "npm run type-check -- --watch",
-    "build": "babel src/ --out-dir lib/ --copy-files --ignore __tests__",
+    "build": "npm run build:types && npm run build:js",
+    "build:types": "tsc --emitDeclarationOnly",
+    "build:js": "babel src/ --out-dir lib --extensions \".ts,.tsx\" --ignore __tests__",
     "precommit": "lint-staged",
@@ -51,0 +53,0 @@ "prepublish": "in-publish && npm run lint && npm run build || not-in-publish"

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

Filesystem access

Supply chain risk

Accesses the file system, and could potentially read sensitive data.

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

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

Improved metrics

Total package byte prevSize

17114

increased by2.57%

Number of medium supply chain risk alerts

1

decreased by-50%

Worsened metrics

Number of package files

12

decreased by-20%

Number of low supply chain risk alerts

3

increased by200%

No dependency changes