James Aprosail

It's not difficult to implement such feature. But the question is whether such changes to source code structure and APIs are acceptable: 1. API changes to the `cleanDir` type: from...

> Bundler itself isn't aware of multiple configs. Yea, it's much complex than I thought... The `Bundler` is called by node side rather than rust side, that it's impossible to...

Another idea, but might make it more complex: 1. Keep original rust implementations, and add warning when might be duplicate cleanings. 2. Add another input options called something like `safeCleanOutDirs`,...

Writing plugin is also not a good solution to avoid duplicated clean dir, because other plugins might modify the output options that the behavior is also not predictable. That's something...

Yes, I'm not sure about that. If that's not something against current design principle, I'll try it later in another Issue&PR when I have enough time (consider that the rust...

... Okay, I quit that idea. It's not a serious enthusiasm, I just wanna to solve a (not important) problem in my personal codebase, and there will be many other...

I finally found out the reason 🥲: It's neither the matter about Deno, nor its VSCode extension, it's just a conflict with other extensions. I was using an AI assist...

[rollup-plugin-dts](https://github.com/Swatinem/rollup-plugin-dts) is released under [copyleft LGPL-3.0](https://github.com/Swatinem/rollup-plugin-dts?tab=readme-ov-file#license), while this plugin (unplugin-dts) is released under [the MIT License](https://github.com/qmhc/unplugin-dts/blob/main/packages/unplugin-dts/LICENSE). A MIT-licensed project cannot use a GPL-licensed project as dependency.