Add NPM as a provider
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- tooling
Research direction
Start by reading the NPM registry example in the issue and the related discussion in issue #806 to understand the provider and fallback context. Done means LibraryManager supports NPM as a provider and can retrieve packages such as chart.js from the registry without relying on a community provider.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Using LibMan puts the chosen provider as a critical dependency of your build. This is expected, but also risky, especially since we're talking about unofficial ones. If the provider fails, all your builds will fail (unless there can be a secondary one: https://github.com/aspnet/LibraryManager/issues/806). NPM can have outages as well, but I'd consider using it an easier sell than community projects, even if they're awesome.
Furthermore, using NPM feels a bit more secure as well to avoid supply chain attacks.
Describe the solution you'd like
Add NPM as a new provider. While not obvious, you can also download the packages from NPM via HTTP. E.g. this one is for the current latest chart.js package: https://registry.npmjs.org/chart.js/-/chart.js-4.5.1.tgz.
Describe alternatives you've considered
Having secondary providers: https://github.com/aspnet/LibraryManager/issues/806.
Additional context
Nothing else.
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
NavigationViewItemAutomationPeer implements IInvokeProvider but never advertises the Invoke pattern Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
unoplatform/uno#24629 ·
-
agentic-workflows Needs: Triage :mag: State: In-PR
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Down / Waiting for removal
Difficulty 2/5 1-3 hours Newbie friendliness 70/100