maierfelix / maierfelix/webgpu
Making WebGPU-NAPI addon @webgpu compliant
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 248
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
I just posted an update to your issue in CTS
Could you please create a cts-napi branch here to develop against the napi branch in CTS?
The basic issue is that there are slight differences in WebGPU API between these two repos that should be resolved. The idea to to make everything compliant with the @webgpu spec.
This will likely mean the addition of typescript to the examples here, to ensure the NAPI addon remains compliant and is instantly aware of changes to the @webgpu spec.
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 by comparing this repository with the CTS cts-napi branch and the linked NAPI branch in CTS. Review the examples and the @webgpu/types package to identify the API differences that need resolution. Done means the addon and examples remain compliant with the @webgpu spec and the cts-napi development path is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, node.js, typescript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100