Proposal: change the default provider from cndjs to an NPM-based provider
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the UI wizard's provider selection and the generation of the default libman.json file. Review the telemetry and provider reliability questions before choosing a default; done means an NPM-supporting provider is the default while Cdnjs remains supported.
Written by the indexing model from the issue text.
Description
Currently Cdnjs is the default provider in both the UI wizard and the default generated libman.json file. However, the Cdnjs catalog is a curated set of libraries; it does not include all libraries from NPM, and it does not include pre-release versions of well-known libraries.
Some feedback we have received indicates that users expect to find any NPM library in the default experience. These searches will fail against the Cdnjs catalog due to its selective curation.
The proposed change would make one of the other providers which does support NPM to be the default. Cdnjs will continue to be supported.
If we move forward with this, we should also consider:
- Can we tell from telemetry which providers are being used today? Will this change better meet current usage trends, or deviate from them?
- Can we determine reliability statistics for each provider? (Cdnjs was initially picked as a default because of unreliable downloads elsewhere)
- 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