So I had to setup a new PC to work with my existing elm projects, and I had forgotten to copy my .ssh key for accessing my repo before running elm-install, resulting in elm-install failing when fetching packages from my private repo.
The issue is that, once this happens, elm-install will then always fail when trying to fetch that specific package, because it tries to access the '.git' folder in the package's path but it does not exist.
The error it displays goes something like "path does not exist", and the path it tries to fetch, when we display it using --trace, is "C:/Users/myuser/.elm-install/my.repo.com/namespace/repo.git/.git".
The only way to fix this right now is to delete the package's folder, and re-run the command. Maybe the package's directory should not be created if it cannot be accessed? Or maybe the case where the .git folder is not existing should be handled as if the package has never been fetched. I feel like this error is a bit counter-intuitive.
So I had to setup a new PC to work with my existing elm projects, and I had forgotten to copy my .ssh key for accessing my repo before running elm-install, resulting in elm-install failing when fetching packages from my private repo.
The issue is that, once this happens, elm-install will then always fail when trying to fetch that specific package, because it tries to access the '.git' folder in the package's path but it does not exist.
The error it displays goes something like "path does not exist", and the path it tries to fetch, when we display it using --trace, is "C:/Users/myuser/.elm-install/my.repo.com/namespace/repo.git/.git".
The only way to fix this right now is to delete the package's folder, and re-run the command. Maybe the package's directory should not be created if it cannot be accessed? Or maybe the case where the .git folder is not existing should be handled as if the package has never been fetched. I feel like this error is a bit counter-intuitive.