Current `make watch` target fails to find `air` even after successful installation about go-blueprint

[smantic]

$GOPATH itself is not deprecated, what this was doing was fine. https://blog.smantic.dev/posts/gopath-is-not-deprecated/

What is deprecated is using $GOPATH as the workspace for go projects. This was typically where you developed go codebases before go modules.

read -p "Go's 'air' is not installed on your machine. Do you want to install it? [Y/n] " choice; \
if [ "$$choice" != "n" ] && [ "$$choice" != "N" ]; then \
    go install github.com/cosmtrek/air@latest; 
    \air;\
echo "Watching...";\

This assumes that the user has added $GOBIN ($GOPATH/bin) to the user's path. This isnt a thing that happens automatically. The previous implementation did not assume that the user had $GOBIN in their path.

[andrerocco]

Yess @smantic, the description of the issue is indeed wrong, thanks for pointing it out.

My experience (and from issue #111 apparently) was that the previous implementation ran on every run of make watch. So it would install air on the system but not detect the installation afterward. Then I think neither the previous implementation should be relied upon.

I'm currious to see if people will have issues with the new implementation as you said that. I will take look into what could solution could be taken to make this as more generalized (work on more machines) as possible.