"cannot find package" errors could be more informative
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.2k
- Forks
- 573
- PR merge metrics
- No merged PRs in 30d
Description
Consider this error from gopherjs build:
cannot find package "github.com/flimzy/flashback/pages" in any of:
/usr/local/go/src/github.com/flimzy/flashback/pages (from $GOROOT)
/home/jonhall/go/src/github.com/flimzy/flashback/pages (from $GOPATH)
It's almost identical to the same error from go build:
cmd/server/server.go:4:2: cannot find package "oink" in any of:
/usr/local/go/src/oink (from $GOROOT)
/home/jonhall/go/src/oink (from $GOPATH)
Except that the go version tells me where the missing dependency is referenced ("cmd/server.go:4:2").
It would be very handy if GopherJS did the same thing :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gopherjs build error-reporting path for missing packages and compare it with the go build diagnostic shown in the issue. Trace where package references are available, then verify that the final error includes the referencing file and position like cmd/server/server.go:4:2.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100