Setup CI for publishing of the package
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 18
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
As part of the goals of the project we've called out publishing a package to NPM for easy consumption by implementors.
Contributor guide
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
Read the linked project goals in issue #15 first, then inspect the repository's package metadata and CI configuration to determine how publishing is expected to work. Done means CI reliably publishes the package to NPM so implementors can consume it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100