I am not sure I understand your objection. I don't think Nimble has anything to do with the project being web related or not.
For one thing, Nimble is not only a dependency manager, but also a task runner: you can use Nimble to run nimscript tasks (I am not sure how to invoke tasks from the command line without using Nimble) Second, while Nimble does not manage non-Nim dependencies, it can still be useful to isolate those dependencies which **are** pure Nim. Global installs can bite you in bad ways, and minimizing those is still useful. In fact, I gather from your response that you consider Nimble not suitable for enterprise work - let me just mention that a system that works in much the same way (Maven) is one of the most enterprisey things I can think of. > Only the build-system, not Nimble, can fetch source-code for dependencies. This, I don't understand at all. Nimble **is** a build system, and one of its main tasks is in fact fetching source-code for dependencies. At least if your deps are all Nim (that is, excluding your objection 2), the reason d'être of Nim is to build stuff with complete knowledge of the dependency tree.
