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

Release [email protected]

Abierto
#687 17 comentarios 8 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
nodejs, typescript
Área
release, tooling

Línea de trabajo

En el issue no se identifica ningún archivo, prueba ni punto de entrada. Empieza revisando la solicitud de release y las discusiones enlazadas sobre TSC, Corepack y Node.js, y después confirma la decisión de los maintainers; se considera terminado si se publica [email protected] o si se documenta un plan de seguimiento concreto para ese release.

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

Descripción

Is your request related to a problem? Please describe.

On 2025-03-19, the Node.js TSC voted to stop distributing corepack in Node.js v25+

Corepack will continue to be available on npm, but users have to globally install it using npm install -g corepack. If users install it from npm, they don't have to run corepack enable like they have to when using the version distributed through npm.

However, there are users who like corepack to manage their package manager versions and would like to continue globally installing it. There are many sources for this.

Many folks in the software industry associate v1.0.0 as stability. There are some who consider everything with 0.x as unstable irrespective of the popularity or usage. As corepack is not going to be distributed though Node.js, the users have to globally install it with npm install -g corepack. Although it doesn't show version, there are some users who might check the latest version on npm and may not install it if it's still 0.x

At the time of comment, the latest version of corepack is v0.32.0. There are enough data points provided above that v1.0.0 can be published. The release of [email protected] will not affect it's experimental status in Node.js core while it's distributed in <=v24.

Describe the solution you'd like

If maintainers think it's ready, please release [email protected] so that the users who associate 0.x with instability will no longer hesitate to install corepack.

If maintainer thinks it's not ready, please use this issue or create a new issue/milestone/label for tracking the v1.0.0 release.

Describe alternatives you've considered

I personally don't have any issue with using corepack while it's 0.x

For folks who do, we can create documentation similar to what other popular tools who're on 0.x have done, like esbuild or ReactNative.

Additional context

This was suggested in https://github.com/nodejs/corepack/issues/104#issuecomment-2746172451

Lenguaje dominante
TypeScript
Estrellas
3.8k
Forks
281
Merge medio
1 h 47 min
PR fusionados (30 d)
2

Preparar el entorno

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 nodejs/corepack

Todos los issues de nodejs/corepack

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.