(#pysczza) ahh this is useful the go culture doesn't typically have large dependency graphs like Ruby or JS.

(#pysczza) @prologic I'm missing something here, does this allow to remap a local module with it, or is just a reference for the whole project/module locally?

(#pysczza) @prologic ahh ok. Do you can now use local relativ air absolute path‘s? that was not possible before iirc

(#pysczza) @justamoment You most always either `go get ... ` or run `go mod tidy‘ -- Building won't install/fetch dependencies not already cached.`

(#pysczza) @lyse this is what confused me the most. But also Python is confusing in this case. Java does a good job here with the packages. Go, when you develop outside the gopath, can get as you described, weird too

(#pysczza) @prologic yes I discovered first hand. 😎

(#pysczza) @justamoment I found that part is well documented 🙂 So, to understand the theory I started here And a few explanations in SO helped me to practice it in my project:

(#pysczza) @prologic the `go get` and `go mod tidy` wont fetch new changes. that's all a manual affair AFAIK

(#pysczza) @justamoment 👌

(#pysczza) @eaplmx Thank you so much. I got the fact that everything get bundled from a single folder but I too am used to properly specify what I want for every module since using Python/JS. On my tries I managed to do local imports and compile with `GO111MODULES` but I was confused on the uses of that flag. Online everything mentioned the url as a reference to the source and I was missing the point of using it locally from a single project. On a post the recommendation was to not use folder which is pretty bad in my opinion for a bigger project, also looking at yarn repo didn't cleared up my doubts (too big for me right now 😓). Thanks again!