Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
MIT License
🔏 sha-sum of the package on npm: 6671b5d117dfb2e7e64c790d3f7fd457091fc281
🔏 shasum: b1c6fe3fd685f6d0a567549c431485235c4791bc
🔏 sha-sum: ad728a8e510c65b1887970e5396f45d0e2b5321e
You can use this e.g. in conjunction with GitHub actions job summaries to make dependency-cruiser's output appear there in a snazzied-up shape.
# ...
steps:
- name: Saving dependency check report to the job summary
run: depcruise src --config --output-type markdown >> $GITHUB_STEP_SUMMARY
# ...
... which then could look something like the example below in its most expanded form. It's possible to only emit parts of it - see the markdown option documentation for details.
Forbidden dependency check - results
📈 Summary
495 modules 1224 dependencies 1 errors 0 warnings 5 informational 0 ignored
rule violations ignored explanation ❕ not-reachable-from-folder-index 3 0 (sample rule to demo reachable rules with capturing groups) ❕ utl-module-not-shared-enough 2 0 (sample rule to demo demo rules based on dependents) ❗ not-unreachable-from-cli 1 0 This module in the src/ tree is not reachable from the cli - and is likely dead wood. Either use it or remove it. If a module is flagged for which it's logical it is not reachable from cli (i.e. a configuration file), add it to the pathNot in the 'to' of this rule. 🔥 All violations
violated rule from to ❗ not-unreachable-from-cli src/schema/baseline-violations.schema.js
src/schema/baseline-violations.schema.js
❕ not-reachable-from-folder-index src/cli/format.js
src/cli/format.js
❕ not-reachable-from-folder-index src/cli/tools/wrap-stream-in-html.js
src/cli/tools/wrap-stream-in-html.js
❕ not-reachable-from-folder-index src/cli/validate-node-environment.js
src/cli/validate-node-environment.js
❕ utl-module-not-shared-enough src/utl/array-util.js
src/utl/array-util.js
❕ utl-module-not-shared-enough src/utl/wrap-and-indent.js
src/utl/wrap-and-indent.js
[email protected] / 2022-06-06T17:54:43.948Z
🔏 shasum: ba3d5cdb800a9a3bb04dc0ede2252d95c96163a0
Thanks @ronalson for raising the issue that led to making the --init option more intuitive for jsconfig.json
s.
🔏 shasum: 1463295cfda195dbddac2528ca144fa702e7679f
🔏 shasum: 81e76968cdd74fcb8e197516368f5958a9b8664c
🔏 shasum: e8390c1acb2fec171ff01b4aa8eadc6a0bcd4102
🔏 shasum of the published package: 11b85bc9e189c25a511568d3a522da8ed30254bf
9bb67861 feature(report): show folder cycles in textual reporters (#580)
3c83b7a5 feature(validate): adds possibility to validate folder cycles (#579)
a0f60782 feature(enrich): detect folder cycles (#578)
79f4c11c bugfix(faq): correct links (#577)
39676fe9 build(npm): update external dependencies
🔏 shasum of the published package: fda117dfd09c5f10a1c2fe68dff9384f58f4c818
Published by sverweij over 2 years ago
🔏 shasum of the published package: d1dab68baf8d1d6481bc373ba1211757ff868ce5
You might have noticed the publishing e-mail address for this package on npm also change from one on yandex.com to one on yahoo.com. This is intentional.
🔏 shasum of the published package: 0a66cb83bd492a35d60e009436dc5951760461f4
Published by sverweij almost 3 years ago
Published by sverweij almost 3 years ago
This is a release of the v10 branch of dependency-cruiser. v10.9.0 contains the same changes as v11.1.0, with the exception of the ones listed below. On npm the v10 branch is published with the version-10
tag.
Published by sverweij almost 3 years ago
This change is breaking only if you
In these cases rules might be triggered that weren't triggered before. When this occurs you can either fix the violations or temporarily ignore them (See --ignore-known in the documentation).
Thanks @rklos for raising the issue and for writing the pull request!
This change is breaking only if
options.enhancedResolveOptions.extensions
in your .dependency-cruiser.js AND.d.ts
and didn't specify .ts
AND.d.ts
modulesIn these cases rules might be triggered that weren't triggered before. When this occurs you can either fix the violations or temporarily ignore them (See --ignore-known in the documentation).
Published by sverweij almost 3 years ago
Version 11 will be published soon. As an experiment we'll back port non-breaking features & fixes to v10 for some time when possible - these will be published on npm under the version-10
tag (latest
will from the next release on be reserved for v11).