WASM fork of vecty. Hopefully temporary
Switch branches/tags
Nothing to show
Clone or download
bketelsen Merge pull request #5 from pichiw/value-fixes
added new "JSValuer" for more direct way to override
Latest commit 9c5e572 Sep 18, 2018
Failed to load latest commit information.
doc namespace Jun 22, 2018
elem namespace Jun 22, 2018
example namespace Jun 22, 2018
prop namespace Jun 22, 2018
style namespace Jun 22, 2018
testdata add new data-driven test suite + move all existing tests to it (#178) Dec 10, 2017
.gitignore add new data-driven test suite + move all existing tests to it (#178) Dec 10, 2017
.travis.yml Merge pull request #141 from shurcooL/patch-1 Sep 5, 2017
CONTRIBUTORS Add contributor tbruyelle (#177) Nov 27, 2017
README.md namespace Jun 22, 2018
dom.go removing prints Jul 8, 2018
domutil.go Keyed children allow for efficient rendering of reordering children Oct 1, 2017
markup.go Merge branch 'master' into wasm-wip Jul 5, 2018
markup_test.go Separate Markup from children. Aug 28, 2017
testsuite_test.go add new data-driven test suite + move all existing tests to it (#178) Dec 10, 2017
value.go made so it requires caninterface Jul 7, 2018


Vecty is a React-like library for GopherJS so that you can do frontend development in Go instead of writing JavaScript/HTML/CSS.

Build Status GoDoc codecov


  • Share frontend and backend code.
  • Write everything in Go -- not JS/HTML/CSS!
  • XSS protection: unsafe HTML must be explicitly denoted as such.
  • Reusability: share components by making Go packages that others can import!


  • Simplicity
    • Keep things as simple as possible to understand for newcomers.
    • Designed from the ground up to be easily mastered (like Go)!
  • Performance
    • As efficient as possible, make it clear what each operation in your webpage will do.
    • Same performance as just using plain JS/HTML/CSS.
  • Composability
    • Nest components to form your entire user interface, seperate them logically as you would any normal Go package.

Current Status

Vecty is currently considered to be an experimental work-in-progress.

  • APIs will change.
  • The scope of Vecty is only ~80% defined currently.
  • There are a number of important open issues.

For a list of projects currently using Vecty, see the doc/projects-using-vecty.md file.



See the doc/CHANGELOG.md file.