npm-merge-driver-install
Advanced tools
A package to install npm-merge-driver locally and automatically.
A package to automatically merge package-lock.json conflicts. Heavily based on npm-merge-driver with automated setup at package install time and a single small dependency for ci checking.
Table of Contents generated with DocToc
To install run
npm i --save-dev npm-merge-driver-install
then add a prepare script in package.json like the following:
{"prepare": "npm-merge-driver-install"}
create a prepare.js file and change your prepare script to the following:
// NOTE: you can use is-ci here or other custom code
const isCI = require('is-ci');
const npmMergeDriverInstall = require('npm-merge-driver-install');
if (!isCi) {
npmMergeDriverInstall.install();
}
then change the prepare script in package.json to
{"prepare": "node prepare.js"}
npm-merge-driver-install: install npm merge drivernpm-merge-driver-uninstall: uninstall npm merge drivernpm-merge-driver-merge: the internal merge binary used to merge package.json and package-lock.jsonnpm-merge-driver-is-installed: check if npm-merge-driver-install is installedFAQs
A package to install npm-merge-driver locally and automatically.
We found that npm-merge-driver-install demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.