TL;DR: Not likely, if you only use the command line interface
:woman: I use the command line interface
When you have rules defined on dependency type type-only or on the
aliased-* ones, dependency-cruiser might start to report issues it didn't
in previous versions as it now more precisely detects those.
03bdda23 fix(resolve)!: makes alias type derivation more correct and precise BREAKING (#867)
05d97951 feat!: restructures the via* sub-restrictions to also accept & validate against dependency types (BREAKING for API users) (#894). See rules-reference.md#circular for details.
before: in rules cycles can be restricted with the restrictions via, viaOnly, viaNot and viaSomeNot, each of which would accept a regular expression (or an array of them) to match against the module names in the cycle.
after: in rules cycles can be restricted with the restrictions via and viaOnly each of which takes an object with the following properties:
path: a regular expression (or an array of them) to match against the module names in the cycle.
pathNot: a regular expression (or an array of them) to match against the module names in the cycle.
dependencyTypes: an array of strings (dependency types) match against the dependency types in the cycle.
dependencyTypesNot: an array of strings (dependency types) match against the dependency types in the cycle.
c6421e3c feat!: makes entries in 'cycle' contain more information (BREAKING for API users) (#888)
before: a cycle in the dependency graph would be reported as an array of strings (the module names)
after: a cycle in the dependency graph is reported as an array of objects with the following properties:
name: the name of the module
dependencyTypes: the types of dependency the module has with the previous
module in the cycle.
e8cda75a feat!: makes entries in reachability via's contain more information (BREAKING for API users) (#895)
before: a route ('via') in the dependency graph would be reported as an array of strings (the module names)
after: a route ('via') in the dependency graph is reported as an array of objects with the following properties:
name: the name of the module
dependencyTypes: the types of dependency the module has with the previous
module in the route.
:heart: Thanks
@camillef - for raising the clear & complete issue that asks to check against dependency types over the entire cycle for circular dependencies
@alvaro-cuesta - for the PR that made the type-only detection more precise
@throrin19 - for raising #863 that led to better detection of aliased-* dependencies and for testing the fixes
@stelescuraul - on adding a test case for workspace aliases on that issue and for testing the fixes for them
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps dependency-cruiser from 15.5.0 to 16.0.0.
Release notes
Sourced from dependency-cruiser's releases.
... (truncated)
Commits
0d70164
16.0.0c5eea78
chore(test): raises branch coverage limitbfb3e2b
build(npm): updates external dependencies52dee75
doc(types): swaps the comments for via and viaOnly7af8569
revert 'feat(init): reduces the moduleSystems in the template to cjs and es6'e8cda75
feat!: makes entries in reachability via's contain more information (BREAKING...05d9795
feat!: restructures the via* sub-restrictions to also accept & validate again...97e7c03
doc(options-reference): fix typo in swc dependency (#893)0278445
feat(extract): adds "pre-compilation-only" to the dependencyTypes as well, wh...7ddf2db
feat(cache): adds cache format version & checks against it (#891)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show