force-dedupe-git-modules
Advanced tools
Comparing version 0.1.7 to 0.2.0
{ | ||
"name": "force-dedupe-git-modules", | ||
"version": "0.1.7", | ||
"version": "0.2.0", | ||
"description": "forcibly dedupes the git-based NPM modules in node_modules", | ||
@@ -5,0 +5,0 @@ "license": "MIT", |
@@ -11,2 +11,2 @@ force-dedupe-git-modules | ||
The command forcibly dedupes the modules in node_modules that were obtain from git (i.e. the value-part of the dependency section in package.json is "git+ssh"), by moving all the git-based modules in dependency chain to right below the "./node_modules" directory, preserving the newest version among all of the installed ones. | ||
The command forcibly dedupes the modules in node_modules that were obtain from git (i.e. the value-part of the dependency section in package.json is "git", "git+http", "git+https" or "git+ssh"), by moving all the git-based modules in dependency chain to right below the "./node_modules" directory, preserving the newest version among all of the installed ones. |
Sorry, the diff of this file is not supported yet
New author
Supply chain riskA 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
4942
1