chore(deps): update dependency dts-bundle-generator to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dts-bundle-generator	^8.0.1 -> ^9.0.0

---

Release Notes

timocov/dts-bundle-generator (dts-bundle-generator)

v9.3.1: 9.3.1

Compare Source

Fixing one little oopsie from v9.3.0 release.

Fixed

• Spamming warning log messages while processing variables (see 8ecb56f)

v9.3.0: 9.3.0

Compare Source

Changed

• Do not compile bundled output together as they might have incompatible global declarations (see #​296 and 43c2058)

Fixed

• Not all symbols in a declaration merging are exported (see #​301 and 874f801)
• Namespaced imports/exports don't generate a namespace if they are exported via name (see #​299 and 86fc2ff)
• jsdoc comments are stripped for nodes that were renamed because of the name collision (see #​298 and 2b1b281)
• Do not rename a node if known global name refers to this a symbol of that node (see #​297 and c0a7007)

v9.2.5: 9.2.5

Compare Source

Fixed

• Fixed inlining transitive-dependencies when using inlineDeclareGlobals (see eb03676)

v9.2.4: 9.2.4

Compare Source

Added

• Added a warning if referenced type is not exported because it was renamed due to the name collisions (see #​288, https://github.com/timocov/dts-bundle-generator/issues/286#issuecomment-1886438899 and 262286c).

v9.2.3: 9.2.3

Compare Source

Fixed

• Do not export types if their local name changed because of collisions (unless they were explicitly exported) (see #​286 and 643003f)

v9.2.2: 9.2.2

Compare Source

Fixed

• Added support for var symbol renaming (see #​285) - thanks @​Atrue!

v9.2.1: 9.2.1

Compare Source

Fixed

• Fixed handling globalThis and undefined (as a value) values (see #​282 and 6a132dd)

v9.2.0: 9.2.0

Compare Source

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 af1736f)
• Fixed incorrect import() statement if imported name is imported with renaming (see 9edab0d)
• Fixed wrongly collision-resolved names when a name exists in a global scope (see 25703d7)
• Fixed incorrect output while having re-export via import (see e324b37)
• Fixed incomplete generated namespace while having export * from statements (see 0bd1a19)
• Fixed incorrect generation while using export * from statements (see 0bdbf07 and b27daaa)
• Fixed error while generating namespaced exports via import statements (see 06e531f)

v9.1.0: 9.1.0

Compare Source

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)

v9.0.0: 9.0.0

Compare Source

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)
• Incorrect handling re-export with namespace (see #​274 and #​277)
• Double-underscored names aren't exported (see #​275 and #​276)
• Invalid bundle while using import as statements in the code (see #​184 and #​270)
• Incorrect handling namespaced imports/exports (see #​266)

v8.1.2: 8.1.2

Compare Source

Fixed

• Something went wrong - value cannot be null (see #​265 and #​267)

v8.1.1: 8.1.1

Compare Source

Fixed

• Stack overflow while handling re-exports with circular dependencies (see #​264 and 4429eac)

v8.1.0: 8.1.0

Compare Source

Added

• Added support for .mts and .cts extensions (see #​204)
• Fixed handling re-exports in dependencies (see #​259)

---

Configuration

📅 Schedule: Branch creation - "after 10pm on tuesday" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
resvg-js	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 6, 2024 6:59pm