Publish via NuGet
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I've signed up for a free MyGet subscription (for open-source contributors) which is how @object builds his Simple.OData.Client library.
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 inspecting the repository's existing package and release configuration, then determine what publishing through MyGet or NuGet would require for this JavaScript component. Done should be a documented, successfully published package, but the issue does not name files, tests, or a precise package format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100