npm dependency-cruiser 12.0.0

latest releases: 16.7.0-beta-1, 16.6.0, 16.6.0-beta-1...
2 years ago

🚨 breaking changes

22deced chore: drops support for node 12 and 17 (BREAKING CHANGE) (#681)

What changed

From this version on dependency-cruiser supports node ^14, ^16 and >=18 (which are the ones nodejs supports at the moment ).

Why?

  • Dependency-cruiser follows the support schedule of nodejs - who de-supported node 12 8(!) months ago. 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 17 anymore. You can safely upgrade to node 18 respectively (see the release page on the nodejs website.
  • Node >=14 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 ^14, ^16 or >=18 - which is likely. Low in all other cases (see How to migrate below)

How to migrate

If you still are on one node 12.x or 17.x there's two options:

  • upgrade your node version to a supported version (^14, ^16, ^18 or ^19)
  • keep using dependency-cruiser@11.18.0

✨ features

  • 8f9854d feature: adds support for .d.cts and .d.mts extensions (#680)

🐛 fixes

  • 8b0a987 fix(report): adds a percentage sign to stability metrics in reporters that emit them as values from 0-100 (#685) Thanks to @Daumel for making me aware this was actually confusing.

👷 maintenance

  • 6c89582/ f1ccc8e build(npm): update external dependencies
  • 576a18d chore(test): types .mocharc.js
  • f0cb660 chore(ci): replaces node 18 with node 19 in environments to test against

🔏 sha-sum of this version as published on npmjs: 9b49cb28154272a861c4357deb989919c5bdcdab

Don't miss a new dependency-cruiser release

NewReleases is sending notifications on new releases.