@pnpm/lockfile.merger - npm Package Compare versions

Comparing version 1.0.1 to 1.0.2

lib/index.js

@@ -6,3 +6,3 @@ "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.mergeLockfileChanges = void 0;
+exports.mergeLockfileChanges = mergeLockfileChanges;
 const comver_to_semver_1 = __importDefault(require("comver-to-semver"));
@@ -59,3 +59,2 @@ const semver_1 = __importDefault(require("semver"));
 }
-exports.mergeLockfileChanges = mergeLockfileChanges;
 function mergeDict(ourDict, theirDict, valueMerger) {
@@ -62,0 +61,0 @@ const newDict = {};

package.json

 {
   "name": "@pnpm/lockfile.merger",
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "Merges lockfiles. Can automatically fix merge conflicts",
@@ -30,4 +30,4 @@ "main": "lib/index.js",
     "semver": "^7.6.2",
-    "@pnpm/lockfile.types": "1.0.1",
-    "@pnpm/types": "12.0.0"
+    "@pnpm/types": "12.1.0",
+    "@pnpm/lockfile.types": "1.0.2"
   },
@@ -38,3 +38,3 @@ "funding": "https://opencollective.com/pnpm",
     "@types/semver": "7.5.3",
-    "@pnpm/lockfile.merger": "1.0.1"
+    "@pnpm/lockfile.merger": "1.0.2"
   },
@@ -41,0 +41,0 @@ "exports": {

New alerts

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

Worsened metrics

Total package byte prevSize

10013

decreased by-0.4%

Lines of code

86

decreased by-1.15%

Number of medium supply chain risk alerts

1

increased byInfinity%

Dependency changes

• + Added@pnpm/lockfile.types@1.0.2(transitive)

• + Added@pnpm/types@12.1.0(transitive)

• - Removed@pnpm/lockfile.types@1.0.1(transitive)

• - Removed@pnpm/types@12.0.0(transitive)

• Updated@pnpm/lockfile.types@1.0.2

• Updated@pnpm/types@12.1.0