It's convenient that using gopherjs serve makes all of your GOPATH workspace available in browser via URLs like http://localhost:8080/import/path.

However, some GopherJS projects use the URL as part of the input and may not expect an import path prefix, which would cause unintended issues for it.

I propose having a flag/value that can be passed to gopherjs serve that restricts serving to the specified import path (it doesn't have to be a valid Go package at that location, it's just a path).

For example, if my frontend project is at example.com/foo/bar I want the URL to be http://localhost:8080/index.html, then I could use:

gopherjs serve example.com/foo/bar

Otherwise, if I used gopherjs serve as is now, I'd have to visit http://localhost:8080/example.com/foo/bar/index.html instead.