# This script demonstrates a bug(?) in go list's reporting of dependency errors:
# The location of the first import that encounters the error is used
# for all other imports. This confuses downstream tools, including go/packages and gopls.

env GOWORK=off

go list -e -f '{{range .DepsErrors}}package {{$.ImportPath}}: error at {{.Pos}}: {{.Err}}{{end}}' ./...

# The second assertion (in package q) fails; instead it reports p.go a second time.
stdout 'package example.com/test/p: error at p/p.go:3:8: no required module...'
stdout 'package example.com/test/q: error at q/q.go:3:8: no required module...'

-- go.mod --
module example.com/test

go 1.22

-- p/p.go --
package p

import _ "example.com/missing"

-- q/q.go --
package q

import _ "example.com/missing"