GopherJS Playground: Use minify flag for building playground.js.

[dmitshur]

It seems that the playground compiled .js output is currently build without using the minify flag (-m). I don't see any good reason not to use the flag, is there?

See #11 (comment) for potential file size savings.

I think we should use the minify flag. But let's do it after the existing PR #11 is merged.

[dmitshur]

I'm gonna make a PR for this after #11 is merged.

I'm considering adding a go generate directive:

//go:generate gopherjs build -m playground.go

That way it will be possible to regenerate the .js file using go generate command, and people will not accidentally forget the -m flag in the future. Thoughts on that? I'm a little unsure if it's a good precedent to start using go generate for building .go to .js. After all, we don't use go generate to replace go build. But the alternative would be a Makefile, which is worse. Or is just mentioning gopherjs build -m playground.go in the README better?

[dmitshur]

Wait a minute, that's wrong. I just realized that building playground.go happens as part of update.sh, so I should modify that file instead.

[dmitshur]

Closed via 6c48c8d.