8000 Support building with GopherJS by paralin · Pull Request #360 · go-git/go-git · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Support building with GopherJS #360

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

Closed
wants to merge 2 commits into from
Closed

Conversation

paralin
Copy link
@paralin paralin commented Aug 4, 2021

This PR adds supports building with "gopherjs build."

paralin added 2 commits March 22, 2023 02:58
Signed-off-by: Christian Stewart <christian@paral.in>
Adds a separate build file for wasm and gopherjs environments.

Issues filed relating to no "gopherjs" tag being set - requiring the more
awkward "js,!wasm" condition, as well as the os.Ctime incompatibility:

 - gopherjs/gopherjs#1047
 - gopherjs/gopherjs#1046

Now the "gopherjs build -v" command works in this repository.

Signed-off-by: Christian Stewart <christian@paral.in>
@github-actions github-actions bot added the stale Issues/PRs that are marked for closure due to inactivity label Mar 8, 2024
@github-actions github-actions bot closed this Apr 8, 2024
@paralin
Copy link
Author
paralin commented Apr 8, 2024

Not stale

@pjbgf pjbgf reopened this Apr 8, 2024
@pjbgf
Copy link
Member
pjbgf commented Apr 8, 2024
< 8000 /div>

@paralin this PR needs a rebase. Is the first commit still needed?

Please add tests to ensure this works (and to avoid future regression).

@paralin
Copy link
Author
paralin commented Apr 8, 2024

I will rebase it.

Not sure how to add test cases when the CI never runs the build with gopherjs nor with the gopherjs tag set.

@pjbgf
Copy link
Member
pjbgf commented Apr 8, 2024

Are you using go-git with GopherJS? If so, we could add a new CI workflow to test that and ensure we don't break support going forwards. Something around the lines of the JS and/or wasm workflows we have in go-billy could work here.

@paralin
Copy link
Author
paralin commented Apr 8, 2024

I am not currently as it does not yet support go1.20, go1.21, go1.22

However, there is effort underway to get it up to spec with go1.22 and once that completes I will test it & likely use it.

If you want, we can close this for now and I'll reopen it if I use gopherjs again.

@pjbgf
Copy link
Member
pjbgf commented Apr 9, 2024

@paralin thanks for the quick reply. Let's close it for now as we are due a bump out of Go1.19, and reopen once they support the latest Go versions.

@pjbgf pjbgf closed this Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues/PRs that are marked for closure due to inactivity
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0