List view

• Go 1.21 support

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• Windows support

  Bug and improvements related to using Windows as a platform for GopherJS development.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• Better developer experience

  Bugs and improvements related to developer experience with GopherJS, such as: - Better error messages. - Linting support.

  No due date

  •8/21 issues closed
  38% complete13 open8 closed

• Go spec compliance

  Bugs and improvements related to GopherJS's compliance with the Go specification, such as: - Correctness of the code generated by the GopherJS compiler. - Runtime behavior deviations from `gc`.

  No due date

  •12/28 issues closed
  42% complete16 open12 closed

• Output size reduction

  Bugs and improvements for the size of the code generated by GopherJS, such as: - Dead code elimination. - Minification. - Bundling and module splitting. - Better code generation.

  No due date

  •1/4 issues closed
  25% complete3 open1 closed

• JavaScript interoperability

  Bugs and improvements related to Go-to-JavaScript interface provided by GopherJS, such as: - API changes to the `.../gopherjs/js` package. - Support for `js` struct field tag. - Support for JavaScript module systems (CommonJS, ES6 modules, etc.)

  No due date

  •6/23 issues closed
  26% complete17 open6 closed

• Runtime performance

  Bugs and improvements related to execution performance of GopherJS-generated code.

  No due date

  •1/7 issues closed
  14% complete6 open1 closed

• Improved source map support

  Bugs and improvements related to source maps generated by GopherJS.

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• cmd/go Build Tool

  This is the milestone to resolve the https://github.com/gopherjs/gopherjs/issues/388 plan.

  No due date

  •2/2 issues closed
  100% complete0 open2 closed