Repository files navigation

GopherJS compiles Go code (go.dev) to pure JavaScript code. Its main purpose is to give you the opportunity to write front-end code in Go which will still run in all browsers.

• ⤴️Help us make better decisions by filling a quick 15-questionGopherJS user survey.
• 📢 Report and discussissues.
• 🎓 Share your knowledge and experience througharticles anddocumentation.
• 🛠️ Write GopherJSbindings for other libraries orcontribute to GopherJS itself.

• 2025-08-19: Go 1.19 beta2 isreleased, with full generics support!
• 2024-02-24: Go 1.19 support isavailable!
• 2022-08-18: Go 1.18 support isavailable!
• 2021-09-19: Go 1.17 support is available!
• 2021-08-23: Go Modules are now fully supported.
• 2021-06-19: Completesyscall/js package implementation compatible with the upstream Go 1.16.
• 2021-04-04:Go 1.16 is now officially supported! 🎉 🎉 🎉

Give GopherJS a try on theGopherJS Playground.

Nearly everything, including Goroutines (compatibility documentation). Performance is quite good in most cases, seeHTML5 game engine benchmark. Cgo is not supported.

GopherJSrequires Go 1.19 or newer. If you need an older Goversion, you can use anolder GopherJS release.

Install GopherJS withgo install:

go install github.com/gopherjs/gopherjs@v1.19.0-beta2  # Or replace 'v1.19.0-beta2' with another version.

If your local Go distribution as reported bygo version is newer than Go 1.19, then you need to set theGOPHERJS_GOROOT environment variable to a directory that contains a Go 1.19 distribution. For example:

go install golang.org/dl/go1.19.13@latestgo1.19.13 downloadexport GOPHERJS_GOROOT="$(go1.19.13 env GOROOT)"  # Also add this line to your .profile or equivalent.

Now you can usegopherjs build [package],gopherjs build [files] orgopherjs install [package] which behave similar to thego tool. Formain packages, these commands create a.js file and.js.map source map in the current directory or in$GOPATH/bin. The generated JavaScript file can be used as usual in a website. Usegopherjs help [command] to get a list of possible command line flags, e.g. for minification and automatically watching for changes.

gopherjs uses your platform's defaultGOOS value when generating code. SupportedGOOS values are:linux,darwin. If you're on a different platform (e.g., Windows or FreeBSD), you'll need to set theGOOS environment variable to a supported value. For example,GOOS=linux gopherjs build [package].

Note: GopherJS will try to write compiled object files of the core packages to your $GOROOT/pkg directory. If that fails, it will fall back to $GOPATH/pkg.

If you want to usegopherjs run orgopherjs test to run the generated code locally, install Node.js 18 (or newer).

On supportedGOOS platforms, it's possible to make system calls (file system access, etc.) available. Seedoc/syscalls.md for instructions on how to do so.

gopherjs serve is a useful command you can use during development. It will start an HTTP server serving on ":8080" by default, then dynamically compile your Go packages with GopherJS and serve them.

For example, navigating tohttp://localhost:8080/example.com/user/project/ should compile and run the Go packageexample.com/user/project. The generated JavaScript output will be served athttp://localhost:8080/example.com/user/project/project.js (the .js file name will be equal to the base directory name). If the directory containsindex.html it will be served, otherwise a minimalindex.html that includes<script src="project.js"></script> will be provided, causing the JavaScript to be executed. All other static files will be served too.

Refreshing in the browser will rebuild the served files if needed. Compilation errors will be displayed in terminal, and in browser console. Additionally, it will serve $GOROOT and $GOPATH for sourcemaps.

If you include an argument, it will be the root from which everything is served. For example, if you rungopherjs serve github.com/user/project then the generated JavaScript for the package github.com/user/project/mypkg will be served athttp://localhost:8080/mypkg/mypkg.js.

There are some GopherJS-specific environment variables:

• GOPHERJS_GOROOT - if set, GopherJS uses this value as the default GOROOTvalue, instead of using the system GOROOT as the default GOROOT value
• GOPHERJS_SKIP_VERSION_CHECK - if set to true, GopherJS will not checkGo version in the GOROOT for compatibility with the GopherJS release. Thisis primarily useful for testing GopherJS against unreleased versions of Go.

• Use the-m command line flag to generate minified code.
• Apply gzip compression (https://en.wikipedia.org/wiki/HTTP_compression).
• Useint instead of(u)int8/16/32/64.
• Usefloat64 instead offloat32.

• #gopherjs Channel on Gophers Slack (invites to Gophers Slack are availablehere)
• Bindings to JavaScript APIs and libraries
• GopherJS Blog
• GopherJS on Twitter
• Examples, tutorials and blogs

The packagegithub.com/gopherjs/gopherjs/js (seedocumentation) provides functions for interacting with native JavaScript APIs. For example the line

document.write("Hello world!");

would look like this in Go:

js.Global.Get("document").Call("write","Hello world!")

You may also want use theDOM bindings, thejQuery bindings (seeTodoMVC Example) or theAngularJS bindings. Those are some of thebindings to JavaScript APIs and libraries by community members.

Set a global variable to a map that contains the functions:

package mainimport"github.com/gopherjs/gopherjs/js"funcmain() {js.Global.Set("pet",map[string]any{"New":New,})}typePetstruct {namestring}funcNew(namestring)*js.Object {returnjs.MakeWrapper(&Pet{name})}func (p*Pet)Name()string {returnp.name}func (p*Pet)SetName(namestring) {p.name=name}

For more details seeJason Stone's blog post about GopherJS.

GopherJS emulates a 32-bit environment. This means thatint,uint anduintptr have a precision of 32 bits. However, the explicit 64-bit integer typesint64 anduint64 are supported.

TheGOOS value of this environment isjs, and theGOARCH value isecmascript. You may use these values in build constraints whenwriting platform-specific code. (GopherJS 1.17 and older usedjs as theGOARCH value.)

Themain function is executed as usual after allinit functions have run. JavaScript callbacks can also invoke Go functions, even after themain function has exited. Therefore the end of themain function should not be regarded as the end of the application and does not end the execution of other goroutines.

In the browser, callingos.Exit (e.g. indirectly bylog.Fatal) also does not terminate the execution of the program. For convenience, it callsruntime.Goexit to immediately terminate the calling goroutine.

Goroutines are fully supported by GopherJS. The only restriction is that you need to start a new goroutine if you want to use blocking code called from external #"auto" data-snippet-clipboard-copy-content="js.Global.Get("myButton").Call("addEventListener", "click", func() { go func() { [...] someBlockingFunction() [...] }()})">

js.Global.Get("myButton").Call("addEventListener","click",func() {gofunc() {    [...]someBlockingFunction()    [...]  }()})

GopherJS Development