-
Notifications
You must be signed in to change notification settings - Fork 570
Support Go 1.13 and Go 1.14 both #964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…t: update for Go1.13
…nge go version request rebuild packages
It's failing because the |
Any news? I have multiple reasons to prefer GopherJS over Go/WASM, but at some point being able to use an up to date version will outweigh the advantages of GopherJS and the headache of migration :-( |
If someone hard forks, I'm happy to migrate over |
@nevkontakte this is from Slack: |
:( Sounds like a fork is in order, then. |
Yes, feel free to create a fork. If it is well maintained for a while, then we can endorse it or maybe even consider a merge at some point. But first Dmitri and I would like to see that the maintenance situation turns out better than what we are currently able to provide. :) |
what should it be called? |
I suggest we either open a new issue, and/or open a slack conversation about this, and other housekeeping details (which organization, who has commit access, etc, etc) so we don't clutter this PR, and so we have a canonical place to point people for posterity. WDYT? |
support work on Go1.15 https://github.com/visualfc/gopherjs/tree/go1.15-dev |
@visualfc Can you merge it to master in your fork so I can use it? I think it's time to adopt yours as the "official" gopherjs. Thanks for the amazing work. |
https://github.com/goplusjs/gopherjs for supported Go 1.12~1.15
|
Does it pass all the go unit tests? |
https://github.com/goplusjs/gopherjs |
@nevkontakte, are you still interested in helping to maintain this project? If so, would you mind adding your name to the document mentioned here? #964 (comment) And if not, that's of course perfectly understandable. |
@flimzy I already have (the second entry) 😃 |
Ha! Sorry I didn't make the connection. And happy you've expressed interest :) |
@visualfc I should have pinged you, too. I know you're making pretty strong headway on your own fork now, so may not be interested in GopherJS any longer, but I want to make sure you have a chance to voice your interest, if you want. #964 (comment) I'm going to try to schedule a call with those interested in helping, to discuss next steps, and if you are interested, of course I'd love to involve you. |
I hope GopherJS can support more go versions. my fork and experiment can support go1.16rc1. |
Does this mean you're not interested in participating in the GopherJS planning call? |
If gopherjs has plans to review PR, I will submit PR again. |
That's clear. Thank you for your response. Hopefully we can start reviewing PRs again soon! |
https://github.com/goplusjs/gopherjs/releases/tag/v1.1.8 support go1.16rc1 go:embed |
I want to make my https://github.com/rocketlaunchr/react package compatible with gopherjs and your package @visualfc . Do you know how I can do it? |
project keep stay import "github.com/gopherjs/gopherjs/js" or use "syscall/js" for compatible wasm |
https://github.com/goplusjs/gopherjs now support Go 1.12~1.16 Go1.12~1.15 test actions on macOS, Go1.16 test action on Ubuntu. |
@visualfc I made a PR in your repo. |
Now that #1015 has been merged, GopherJS is up to date with the latest upstream Go, so I'm going to close this PR. |
Build on Go 1.13 / Go 1.14 and one build support working on Go 1.12 Go 1.13 Go 1.14 three version.
gopherjs build -a -v
orgopherjs test -a -v