atlas/nimble build still tries to download dependencies despite nim.cfg

Awesome, I was aware of the nimble version but did not know that was also an available capability of a config.nims file. That is very helpful, thanks!

atlas/nimble build still tries to download dependencies despite nim.cfg

> That is indeed the intended process and not an interim solution either, it's > Atlas's key feature and design aspect. Got it, thanks! I assumed that the `atlas build` command would be the new way. I am curious to see what that command is renamed/turned into.

atlas/nimble build still tries to download dependencies despite nim.cfg

This sounds great; do you happen to have a public repo using this technique that I could look at?

atlas/nimble build still tries to download dependencies despite nim.cfg

> What's the benefit of nimble build when you use Atlas to manage your deps? Well, I started out trying `atlas build` but of course that is currently an alias for `nimble build`. If the intended process for now is to just use `nim c` then I think that resolves my question, thanks!

atlas/nimble build still tries to download dependencies despite nim.cfg

I have been trying out atlas; really like the premise, and its features are great so far. I have found that `nimble build` doesn't seem to behave correctly alongside, however. But I'm not sure if I'm missing something. If I set up a workspace + project with atlas, I can build it fine via `nim c`

After upgrading to Nim 1.6.12, my tests generate a lot of warnings - how to address?

I actually [reported this on GitHub just yesterday](https://github.com/nim-lang/Nim/issues/21731) :) It was addressed almost immediately by which I imagine will be in the next point release. For now there's a pragma that can silence the warning: