Publishing to npm?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- release
Research direction
Start by comparing the npm package msrcrypto at version 1.5.8 with this library's 1.6.0 release and reviewing the repository's publishing configuration. No source file or test is identified in the issue. Done would require an agreed publishing plan and the library being available under @microsoft/msrcrypto.
Written by the indexing model from the issue text.
Description
Currently https://www.npmjs.com/package/msrcrypto is at 1.5.8 of this library.
This library is at 1.6.0.
Is there a plan to publish this library to npm? under @microsoft/msrcrypto?
- Dominant language
- JavaScript
- Stars
- 69
- Forks
- 33
- Avg merge
- 3d 12m
- Merged PRs (30d)
- 1
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.
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AllTheMods/ATM-10-L#19 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SignalK/n2k-signalk#345 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
JuliaPluto/PlutoPlotly.jl#72 ·