Wrong package name gives infinite errors

[llimllib]

If you use package main instead of package build in a go file in app/pkg, while the server is running in dev mode, I get an infinite list of:

build/cmd/myproject/main.go:18:2: import "example/myproject/build" is a program, not an importable package
build/cmd/myproject/main.go:18:2: import "example/myproject/build" is a program, not an importable package
build/cmd/myproject/main.go:18:2: import "example/myproject/build" is a program, not an importable package

• Is it possible for us to generate a better error?
• The dev server should throw the error once and then not throw it again until something has changed

[paulsmith]

Right now any user-contributed code in app/pkg has to be package build by convention. Will open a new issue to track either documenting this or making it configurable.

[paulsmith]

Is it possible for us to generate a better error?

Currently, building the generated Pushup app is a black box - would like to wrap it, perhaps by inspecting stderr.

The dev server should throw the error once and then not throw it again until something has changed

Agreed, basically any error causes this loop.

[paulsmith]

I think recent changes (specifically baa912f) fixed this. I am no longer able to recreate original buggy infinite loop errors by supplying the wrong package name in dev reload mode.