Dave Brophy

It's not on my short-term to-do list.

Good plan. I'll look into this.

Yep. Supporting `vgo` (or whatever it turns into) is definitely on my roadmap, however it will be a big undertaking. I created an issue (here: https://github.com/golang/go/issues/23951) suggesting a vgo feature...

Thanks for the suggestion! However, in `jsgo` everything runs in the Go process, so without a Go version of `uglify` this wouldn't be possible.

BTW did you run any tests to see what percentage compression uglify gives? GopherJS has it's own minify routine which probably isn't as good as uglify but I wouldn't think...

Adding this to the jsgo compiler would be a huge undertaking. Right now everything runs inside a single Go process - that keeps the architecture very simple. Adding docker as...

Hey I just pushed a v0.0.2 tag of jsgo which fixes a bug in the localfetcher which might resolve this problem... Give it a go and let me know!

Hmm was there anything outputted to the terminal by main.go?

... and how about if you just hit http://localhost:8080/ with no path?

.. and what happens if you hit http://localhost:8081/ ?