Package Exports

dependency-sync

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (dependency-sync) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

dependency-sync

⚡ sync your dependencies ⚡

usage for entry point in module

npx dependency-sync

multiple entry points

npx dependency-sync ./file-1.js ./file-2.js

esm modules & jsx

npx dependency-sync -t babelify

babel and babelify will need to be installed and configured

example package.json

  "devDependencies": {
    "@babel/core": "7.8.4",
    "@babel/preset-env": "7.8.4",
    "@babel/preset-react": "7.8.3",
    "babelify": "10.0.0"
  },
  "dependency-sync": {
    "args": [
      "-t",
      "babelify"
    ]
  }

example babel.config.js

  module.exports = {
    presets: ['@babel/preset-env', '@babel/preset-react']
  }

watch dependency changes

npx dependency-sync --watch

check-only

will exit with error if modules are not in sync

npx dependency-sync --check-only

keep

dependency-sync ignores devDependencies, However dependencies that aren't explicitly required will be removed.

To prevent this add the following directive to your package.json.

"dependency-sync": {
  "keep": [
    "babelify"
  ]
}

yarn

To use dependency-sync with yarn use add the following directive to your package.json.

args is passed to yarn add

"dependency-sync": {
  "yarn": true
}

or with extra arguments

```json
"dependency-sync": {
  "yarn": 
    "args": [ ]
  }
}

dry-run

npx dependency-sync --dry-run

verbose

npx dependency-sync --verbose

license

MIT