npm dependency-cruiser 3.0.0-beta-0

latest releases: 16.3.3, 16.3.2, 16.3.1...
6 years ago
  • 🐣 by default follow symlinks / add --preserve-symlinks option (issue #33, PR #37 thanks @ajafff for the contribution!!)
  • ⬆️ devDependencies: coffeescript, eslint, eslint-plugin-import

Breaking change: symbolic links followed by default

impact classification: low.

By default dependency-cruiser now follows links when resolving dependencies. This is consistent with how NodeJS behaves itself since version 6.

In the unlikely event you use symlinks (e.g. with npm link/ yarn workspaces) and depend on the old behaviour, you can do one of these:

  • use the --preserve-symlinks command line option
  • in the options section of your .dependency-cruiser.json add a preserveSymlinks key with the value true.

Don't miss a new dependency-cruiser release

NewReleases is sending notifications on new releases.