Does go throw an error? Is there a specific import that should be added but isn't?

You are using the word “correctly”, but it isn't at all obvious to me that the observed behavior is “incorrect”. Can you describe what you expected to see and what you did see in terms of the actual dependencies used?

Does go throw an error? Is there a specific import that should be added but isn't?

You are using the word “correctly”, but it isn't at all obvious to me that the observed behavior is “incorrect”. Can you describe what you expected to see and what you did see in terms of the actual dependencies used?

https://github.com/angelofdeauth/xnotify/blob/4263fb794911e4bf6e6350ff262b593ae07843b6/pkg/box/generator.go is a script that is run at build time using go generate, and is called from https://github.com/angelofdeauth/xnotify/blob/4263fb794911e4bf6e6350ff262b593ae07843b6/pkg/box/box.go#L9 via the //go:generate preprocessor tags.
generator.go uses package main as it isn't compiled as part of the module/package and is instead just a one-off which generates a file that is included in the module/package.

Without this line: https://github.com/angelofdeauth/xnotify/blob/4263fb794911e4bf6e6350ff262b593ae07843b6/pkg/box/hack.go#L11 , go mod vendor and go mod tidy do not recognize "github.com/gobuffalo/here" as a project dependency at all, and there is no dependency listed in my go.mod, vendor/modules.txt or files in vendor/{{importname}}.
This is a problem, as when I try to run go generate, it fails stating that the dependency is not found in the current module.

I just realized, it's actually the //+build ignore directive in generator.go https://github.com/angelofdeauth/xnotify/blob/4263fb794911e4bf6e6350ff262b593ae07843b6/pkg/box/generator.go#L9 that's causing this. I would argue the intended behaviour here is still valid, as generator.go should not be built into the final executable, but the tooling functionality does not reflect that ability.

If you don't want the file to be ignored, use a build constraint other than ignore.

(// +build tools is common: see http://golang.org/wiki/Modules#how-can-i-track-tool-dependencies-for-a-module.)

Or, I suppose, if you want the dependency to be resolved dynamically instead of a specific version, set GOFLAGS=-mod=mod or pass -mod=mod explicitly on the go:generate command line, so that go run doesn't try to find the dependency in the local vendor directory.

Duplicate of #29598

Awesome, thanks for the link @bcmills . I've looked at the docs on golang.org, they're less descriptive. This is much more clear.