NuGet-based provider and CDN
还没有人认领这个 Issue。
评估
调研方向
Start by reviewing LibraryManager's existing JSON-based provider protocol and how libman supports other package sources. Then examine the NuGet and nuget.org constraints described in the issue, including arbitrary non-public feeds. Done would require a settled protocol and an agreed implementation scope for source-only NuGet packages and CDN-style references.
由索引模型根据 Issue 内容生成。
描述
For source-only nuget packages with (say) a single (or few) source file, it might be nice to be able to reference them directly just like libman provides for other package sources.
This would require defining a protocol (maybe augmenting the existing json-based one) and either supporting it built-in in nuget.org or allowing arbitrary sources (my preference, since that would also allow non-public feeds too).
- 主要语言
- C#
- 星标
- 486
- 派生
- 91
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aspnet/LibraryManager 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
aspnet/LibraryManager#824 · 1 条评论 · 3 个 reaction ·
-
难度 1/5 1 小时以内 新手友好度 68/100
aspnet/LibraryManager#804 · 2 个 reaction ·
-
难度 1/5 1 小时以内 新手友好度 48/100
aspnet/LibraryManager#829 · 1 条评论 · 3 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 42/100
aspnet/LibraryManager#820 ·
-
难度 4/5 3-5 天 新手友好度 35/100
aspnet/LibraryManager#808 · 5 条评论 ·
查看 aspnet/LibraryManager 的全部 Issue
相似的 Issue
-
core dependencies
难度 1/5 1 小时以内 新手友好度 80/100
-
bug frontend good first issue
难度 2/5 1-3 小时 新手友好度 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
难度 2/5 1-3 小时 新手友好度 70/100
-
Down / Waiting for removal
难度 2/5 1-3 小时 新手友好度 70/100