On Tuesday, May 13, 2025 4:18:19 AM Mountain Daylight Time Denis Feklushkin via Digitalmars-d wrote:
> How to run dub dustmite over exactly one current package code?
>
> dub dustmite at beginning copies package code with all dependencies into dedicated directory and does its work on all of these files.
>
> Or maybe this is only right approach and there is no need to run dustmite only on one current package?

Whether it's the right approach depends on where the problem actually is, but as a general rule, it's probably better to run it on as minimal a piece of code as you can which you know will exhibit the problem, and if that ultimately shows that the problem might be in something that's being imported, then you dustmite that too. The more than you're dustmiting at once, the longer it will take.

That being said, I'm not sure that I even knew that dub had any dustmite support, so I can't comment on what can or can't be done with that. I'd suggest looking at dub's documentation for clues.

I'd probably either figure out the appropriate dmd build commands so that I could build the project without dub in order to dustmite just the project, or I'd let dub copy everything over and then do the build from there with dustmite and put whatever the appropriate comments are from dustmite's documentation on the various files that I didn't want to be dustmited so that it didn't muck with them.

But maybe the dub documentation has something useful to say on the matter. I don't know. All of the dustmiting that I've done has been by using dmd without dub as an intermediary.

- Jonathan M Davis