Document that gopherjs test requires system calls Node module (or make it not require it, if possible).
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.2k
- Forks
- 573
- PR merge metrics
- No merged PRs in 30d
Description
I'm almost certain
gopherjs testworked previously without installing the syscall module (I have never installed it in the past AFAIK). So probably a regression, would be my bet.
See https://github.com/gopherjs/gopherjs/issues/624#issuecomment-294386098 for details.
Edit: Also see #815 for a minimal reproduce case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal reproduce case referenced in #815 and the details linked from #624. Determine whether gopherjs test still requires the Node syscall module; done means either documenting that requirement clearly or confirming the dependency is no longer needed and the reproduce case passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, node.js
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100