chore(deps-dev): bump dts-bundle-generator from 8.0.1 to 9.2.0

[dependabot]

Bumps dts-bundle-generator from 8.0.1 to 9.2.0.

Release notes

Sourced from dts-bundle-generator's releases.

9.2.0

Release notes

In this release I tried to adapt tests from api-extractor tool in order to compare results and apart from some passing tests I found a few issues that are fixed in this release.

Fixed

• Prettified output when some "parts" aren't emitted (e.g. banner) (see af1736f6fccd9b550a5acfe25a966a133d5bc083)
• Fixed incorrect import() statement if imported name is imported with renaming (see 9edab0dd94013e0539de9ea106e79f978ac22f4b)
• Fixed wrongly collision-resolved names when a name exists in a global scope (see 25703d7f422f3590d1a3ccf7e92bd45d1e4fc987)
• Fixed incorrect output while having re-export via import (see e324b3700e728db6971eb97388f93adc8abd066e)
• Fixed incomplete generated namespace while having export * from statements (see 0bd1a19173c069b3413b88a772b236035fd176bf)
• Fixed incorrect generation while using export * from statements (see 0bdbf078a4e7d963765a689b5383f2b7b33b8aea and b27daaabf781a893e11a7adbe486717295940b06)
• Fixed error while generating namespaced exports via import statements (see 06e531f86d161d5794311f046062942e03d4a98b)

9.1.0

Release notes

With this release all known bugs in the tool are fixed (especially long-lived ones!) 🎉

Fixed

• Star re-exports (import * as NS / export * as NS) aren't wrapped with a NS name (see #134 and #281)
• (Re-)Export from re-export from external library doesn't add import/export statements (see #251 and #279)

9.0.0

Release notes

This release is one of biggest and the most valuable releases in years.

It introduces a fix for a limitation that existed since very first release i.e. resolving of name collisions 🎉.

Now, if you have 2 nodes with the same name in the bundle, one of them will be renamed (by adding $NUM suffix) to avoid clashing and accidental declaration merging (but if you have 2 interfaces declared in the same module to have declaration merging it should work as expected too).

Because of this new mechanism it helped to address some of the issues that I wasn't aware of but it seems that it existed in some of the packages, i.e. using a wrong name because of renaming during import (import { name as newName } case) (see "Additional information" section in this PR).

One of known changes in the declaration generation with this release is that a function/class/etc that was originally exported with the default export will never be exported directly but via re-export export { name as default }. This should not affect the result of the bundle but I think it is worth to note it.

But there is more, please refer to the change log below.

Last but not least, I want to thank @​Atrue for the contribution which was a motivation to make this release happen 🙏

Added

• Use language service "rename" functionality to avoid name collisions (see #130 and #270)
• Support for auto renaming nodes with the same name in the bundle (see #116 and #270)

Fixed

• Inlining a library with namespaced imports/exports inlines export statements (see #271 and #278)

... (truncated)

Commits

• 79b373e Bumped version to 9.2.0
• b27daaa Fixed handling re-exports with export * from and renamings while importing/...
• 41e1a5f Removed eslint-plugin-prefer-arrow eslint plugin
• 843c6ed Don't make unnecessary links between symbols
• 5c88857 Prettified code and making less assumptions but validate with checks
• 06e531f Fixed error while generating namespaced exports via import statements
• 0bdbf07 Fixed handling export * from 'mod' in root a source file (and all recursive...
• 0bd1a19 Fixed incomplete generated namespace while having export * from statements
• e324b37 Fixed incorrect output while having re-export via import
• 25703d7 Fixed wrongly collision-resolved names when a name exists in a global scope
• 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 show <dependency name> 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (37b0d88) to head (1edab21).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #965   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines           63        63           
  Branches         2         2           
=========================================
  Hits            63        63           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.