I tried deps-try amazonica "0.3.165"
which results in an error Could not find path '***/amazonica'
I should have tried deps-try amazonica/amazonica "0.3.165"
instead, and then things work as expected.
This might not be obvious for new users. I also had to think for a bit. And this would also not be obvious by reading the README of Amazonica where it is still [amazonica "0.3.165"]
.
When there is no namespace maybe if the directory doesn't exist (in this case amazonica
), deps-try
could try to resolve it as a dependency?
(*) tested with version deps-try-dev v0.8.0
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too