How to Test Local Changes with Go Mod

Teiva Harsanyi

We are developing on two different Go projects using modules:

  • A github.com/acme/bar module
  • Another github.com/acme/foo module that depends on the first one

Let’s say we made some changes to github.com/acme/bar and we would like to test the impacts on github.com/acme/foo before committing them.

Without Go modules, it was pretty straightforward as our changes were done in GOPATH so they were automatically reflected.

With Go modules, the trick is to replace our import by the physical location of the project:

Here, /path/to/local/bar is the actual location of the bar project containing the local changes.

We can also use the following command:

go mod edit -replace github.com/acme/bar=/path/to/local/bar

Voilà.

Teiva Harsanyi

Written by

Software Engineer. Go & Java, Distributed Systems, Concurrency, FP, DDD. 🇫🇷 in 🇬🇧.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade