Attempting to fix modules' indirect depedencies on master #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a
server.SimpleService
is built locally with our current master branch, the go.mod file looks like this:I ended up blowing away the existing go.mod and go.sum in the base of the repo and rebuilding everything. With these changes, it's back to simply importing gizmo:
require github.com/NYTimes/gizmo v1.2.2-0.20190225192859-9d0764c8f4cd
I'm still yet to find the cause of the
gopherjs
packages popping up in our go.sum, but I'm starting to think it has something to do with a test framework used by one of our depedencies.Unfortunately, despite our latest module changes, even building the simplest of simple servers still yields the same results when running
go list
as mentioned in #188. I'm open to suggestions if anyone has any.If anyone is willing to take a shot, I'm using this server as my control during experiments: