Thanks for the WASM build!
Nobody has claimed this yet.
- Dominant language
- G-code
- Stars
- 73
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
It was really easy to add support for parsing bgcode files to my project. Thank you to whomever it was that put the time into adding the wasm/emscripten build.
If I had one suggestion, it would be to not name your global Module. Name it BGcodeModule or something unique. When you get releases sorted out we can write some typescript bindings for it and make an NPM module.
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 WASM/emscripten build and inspect the global Module name referenced in the issue and linked commit 427cffe9fe4fa70b5eccc54cc61b183668a0f5d9. Confirm where the exported global is defined and used; done means the global has a unique name without breaking the WASM interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100