Releases: sverweij/dependency-cruiser
v16.0.0-beta-1
v15.5.0
✨ features
- 8aa2a3d feat(init): adds exception to not-to-dev-dep for type-only dependencies (#874) - thanks to @alvaro-cuesta for the suggestion
- 91f36a5/ 38c4a46 feat(wrap-stream-in-html): adds a gradient on highlighted edges (#878)
📖 documentation
- 9415a84 fix(doc): re-organizes types folder, improves typing of extract-webpack-resolve-config
- 6d808db fix(doc): improves package type exports (#876) making are the types wrong a little more happy
👷 maintenance
v15.4.0
✨ features
- ba4533f feat(resolve): enables passing 'aliasFields' to enhanced-resolve (#870) - thanks to @JakeSidSmith for not only raising the issue that led to this fix, but also for the detailed & well documented research that made this addition a very easy one to implement.
- dfdb385 feat(reporter/dot): only considers rule severity for coloring invalid modules/ dependencies (#869)
🐛 fixes
- 3445a3b fix(init): makes initial regular expressions more specific (#872)- thanks @mx-bernhard for raising the issue and suggesting an elegant fix.
📖 documentation
👷 maintenance
- a6d562b build(npm): updates external dependencies
v15.3.1-beta-2
🐛 fixes to address #863
On top of the commit that takes 'workspaces' field into account when merging package manifests fix from #867, from that same PR:
- 78990e0/ 2f29ace/ 943a521 fixes: don't classify relative module names as 'aliased' - which addresses the bug that bit the beta testers
- give precedence to bolted-on aliases (webpack) over node native aliases might there be a conflict
✨ / 📖 things from the main branch rebased into #863, but not released to latest yet
v15.3.1-beta-1
🐛 fixes
- fe0a831 fix(resolve): takes 'workspaces' field into account when merging package manifests
v15.3.0
✨ features
- fce008d feat(extract): makes support for workspaces explicit (#864)
This should also fix the bug discovered by @throrin19 in #863
👷 maintenance
v15.2.0
✨ features
👷 maintenance
v15.1.1
v15.1.0
v15.0.0
✨ features (🚨 with breaking changes)
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 ...
-
a3cfcec 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. -
36c3dde feat!(extract): makes support for subpath imports explicit BREAKING (#855)
Because dependency-cruiser now labels subpath imports asalias
andalias-subpath-import
instead ofundetermined
:- if you have rules that explicitly check for
alias
dependency-crusier might uncover transgressions it didn't before. - Likewise if you had rules with checks on
undetermined
dependency types to find subpath imports, you might want to update them toalias-subpath-import
- if you have rules that explicitly check for
✨ features
- 08dce74 feat(report): links to npmjs/ nodejs.org for npm respectively node and core modules (#854) thanks to @CaptainQuirk for the question that led to this feature and for the feedback on the first crude prototype.