Validate and visualize dependencies. Your rules. JavaScript, TypeScript, CoffeeScript. ES6, CommonJS, AMD.
MIT License
On top of the commit that takes 'workspaces' field into account when merging package manifests fix from #867, from that same PR:
Published by sverweij 12 months ago
For the majority of use cases these additions are not breaking. For the few use cases that are: dependency-cruiser has gotten a little more precise only ...
a3cfcecf feat!(extract): makes 'real' depencency type available alongside aliases BREAKING (#856)
If you have rules that check for dependencyTypes explicitly the rules will still work as before, but they'll be more effective, potentially uncovering transgressions dependency-cruiser didn't find in earlier versions.
36c3dde9 feat!(extract): makes support for subpath imports explicit BREAKING (#855)
Because dependency-cruiser now labels subpath imports as alias
and alias-subpath-import
instead of undetermined
:
alias
dependency-crusier might uncover transgressions it didn't before.undetermined
dependency types to find subpath imports, you might want to update them to alias-subpath-import
glob
as a candidate for replacement!typings
as a mainFields
wherever types
is suggested (#831) - thanks to @BRMatt for both the research into this and the (clear and well documented) pull request that fixes this!π shasum of the package as published on npmjs: c748333481088f16bb46f15a9d3f8a8699ceb2c7
π shasum of the package as published on npmjs: 38dbbf932fd09955167a22abd0d9876b07a23acf
π shasum of the package as published on npmjs: bc76744d795e5879116b42f81bca39a5e983eae1
π shasum of the package as published on npmjs: 1c15d92229a0d055a55d4c8ae49b81e41234c29c
π shasum of the package as published on npmjs: f82c852fcdad098314a405f3856c470360d61c92
π shasum of the package as published on npmjs: abe600dfd6b7dbd6a5186309ae9ddbdff9e3a3a7
π shasum of the the release as published on npmjs: 2f8ed287ca761340b38a3881a3277a2b0c9cea60