Bump dependency-cruiser from 9.26.0 to 10.0.1

[dependabot]

Bumps dependency-cruiser from 9.26.0 to 10.0.1.

Release notes

Sourced from dependency-cruiser's releases.

v10.0.1

🐛 bugfixes

• e5e3a7d0 bugfix(init): update the doc output of --init experimental-scripts
• 8a866898 bugfix(resolve): work around enhanced-resolve's hashmark-in-filenames problem (#461)

👷 maintenance

• 9ffbe857 build(npm): ⬆️ enhanced-resolve, eslint-plugin-unicorn

v10.0.0

👷‍♀️ maintenance

91e353f3 build: drop support for node <12.20 (💥 breaking change)

What changed?

From this version on dependency-cruiser supports node ^12.20, ^14 and >=16 (which are not coincidentally the same as the ones nodejs supports).

Why?

• Dependency-cruiser follows the support schedule of nodejs - which de-supported node 10 this month. Many of its dependencies also stopped supporting it, so it's getting less easy (and safe!) to maintain that situation.
• Likewise nodejs doesn't support node 13 anymore, and soon won't support node 15 any longer. You can safely upgrade to node 14 and 16 respectively (see the release page on the nodejs website.
• Node 12.20 contains some useful features earlier versions didn't have, which dependency-cruiser either is already using or will start using in the near future.

What is the impact?

None if you're on node 12.20, ^14 or >= 16 which is likely. Low in all other cases (see How to migrate below)

How to migrate

If you still are on one node 10.x, 13.x or 15.x there's two options:

• upgrade your node version to a supported version (^12, ^14, ^16 or even ^17 when that comes out)
• keep using dependency-cruiser@9.26.1

🐛 bugfixes

3fc204d3 bugfix(validate): correctly filter out dependents from pathNot (#460) (💥 breaking change)

What changed?

This is technically a breaking change: if you had a rule with dependents in them and a pathNot attribute in the from part, the validator would treat the paths in pathNot as if they were regular paths. This is obviously wrong, but if your ruleset relies on this erroneous behaviour rules might fire that didn't before.

Thanks @​davidparkagoda who both spotted the error and contributed this bugfix!

Why?

... (truncated)

Commits

• 9c15ddb 10.0.1
• e5e3a7d bugfix(init): update the doc output of --init experimental-scripts
• 8a86689 bugfix(resolve): work around enhanced-resolve's hashmark-in-filenames problem...
• 9ffbe85 build(npm): ⬆️ enhanced-resolve, eslint-plugin-unicorn
• 33f13d0 10.0.0
• 91e353f build: drop support for node <12.20 (BREAKING CHANGE)
• 3fc204d bugfix(validate): correctly filter out dependents from pathNot (#460)
• b5c2c9e 9.26.1
• 1fb78cf build(npm): ⬇️ upem
• 7488a38 doc(plugins): adds an example 3d reporter plugin
• Additional commits viewable in compare view

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]

Superseded by #221.