Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Proposal: change the default provider from cndjs to an NPM-based provider

Abierto
#517 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
csharp
Área
tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)
Lenguaje dominante
C#
Estrellas
486
Forks
91
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aspnet/LibraryManager

Todos los issues de aspnet/LibraryManager

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.