Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
MIT License
π sha-sum of the package as published to npmjs: c20a41fd6cdf7c0b31e18220134cb35dc8d40706
π shasum of the package as published on npmjs: abfa2c7464d063e69f2d8bd369b47f623d38b831
π shasum of this released as published on npmjs: 19ba6f9b1db9f9860301258f5ae097ac27ac69c2
--cache-strategy option
(#724)π shasum of the package as published on npmjs: 5e2c7095ca9544c5805471a8d4e1f9975f411f87
π shasum of the package as published on npmjs.com: fa9ecb771749f05093e6fccd2f5abab137efee57
π sha-sum of the package as published on npmjs: a75fc3a7344d95707952cc220b9770b7f01cda49
π shasum of the package published on npmjs: 441fb999330173eb3ab3c1f1308488e7b174ba9c
π sha-sum of the package as published on npmjs: 1336a2618075e0862b98fe6f3ed5494b584a63e7
π sha-sum of the package as published on npmjs: e2f736e9d6f7b362fd8a35956fbce8f7c88194f0
From this version on dependency-cruiser supports node ^14, ^16 and >=18 (which are the ones nodejs supports at the moment ).
None if you're on node ^14, ^16 or >=18 - which is likely. Low in all other cases (see How to migrate below)
If you still are on one node 12.x or 17.x there's two options:
π sha-sum of this version as published on npmjs: 9b49cb28154272a861c4357deb989919c5bdcdab
π shasum of the package as published on npmjs: 91bdb45298a5e79dba56872ef6ffb4a8770f7081
π shasum of the package published on npm: 1f7afaf1bb4fcfab01877da600317034273c2c98
π sha-sum of the package published on npm: 94904235cc8887b3992770b228b899a54437cdb3
fb208889 doc(README): shows output formats closer to the top (#657)
f8b8e565 doc(cli.md|options-reference): fix broken links in .md: default-theme.js (#658)
Thank you @magland for both of these pull requests!
2f1dbcfe doc(README): restructures 'how do I use it' section (#664)
π sha-sum of the published package on npm: e5e2afaf74d4a8b701c3a93a61fec18608c2d75d
π sha-sum of the package published on npm: 694b083029491091a610665a6fc077673797ce6e
π sha-sum of the published package on npm: 76ca6fbe49130574a12efe0450856cb349106482
This upgrades (a.o.) tsconfig-paths-webpack-plugin
(which was released yesterday) to 4.0.0. So as of now you should be able to use /
at the start of path aliases, which closes #398.
π shasum of the package on npm: 91c6e2113d8992e6e2e849ac292fb710b834eb96