Dmitri Shuralyov

> Does anyone find it useful? I don't remember the last time I've seen it. I might've fixed all instances and not introduced new ones. As a result, it's hard...

I've suggested this idea to @neelance too, and we discussed it. @neelance told me it's a nice to have that is more long term, because it requires quite a bit...

Another important (IMO) benefit of server-side rendering is that it enables a gradual transition path for developers. If vecty rendering API allows for server-side rendering, then users can: 1. Start...

Absolutely. ``` go get -u -d github.com/shurcooL/Go-Package-Store/cmd/Go-Package-Store GOARCH=js go get -u -d github.com/shurcooL/Go-Package-Store/frontend go build -tags=dev -o /tmp/gps github.com/shurcooL/Go-Package-Store/cmd/Go-Package-Store /tmp/gps ``` (Also look over https://github.com/shurcooL/Go-Package-Store#development.) You'll see something like this...

Sorry, unfortunately, I haven't yet added support for sourcemaps to `gopherjs_http` package. You could use the `gopherjs build` to get them there, but that's gonna take some manual work. Also,...

Just reload in the browser. When you use the `dev` build tag, it always builds from source. I'll give that a try, thanks!

Yeah, that seems to have worked. I've made this one line change: ```diff // RepoPresentation is a component for presenting a repository update. // // TODO: Dedup with workspace.RepoPresentation. Maybe....

This is unexpected to me because I thought #130 and the `prop` tag only mattered if I were using `Restorer` interface, which I wasn't. I'll have to spend some time...

If you don't mind, I'm certainly open to considering improvement suggestions in GPS rendering code, thank you. I'll also spend some time reading and learning more about #130, thanks for...

Following up on the `` `vecty:"prop"` `` change. I've applied it in shurcooL/Go-Package-Store#88. It helps fix the originally spotted rendering issue. However, it doesn't completely make the rendering correct, there...