glob@10 is deprecated upstream; upgrading requires dropping Node 16

Abierto
#21 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

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
Refactorización
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
node.js, typescript
Área
tooling

Línea de trabajo

Read the package metadata to confirm the glob version range and supported Node engines, then trace the file-discovery call sites that use glob. Compare the upgrade, replacement, and stay options against compatibility and release policy before proposing a direction. Done means the project has chosen an option and documented its engine and release implications; the issue does not specify a decision or test target.

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

Descripción

enhancement

glob@10 is deprecated upstream. Its own maintainer publishes this on the version we
depend on:

Old versions of glob are not supported, and contain widely publicized security
vulnerabilities, which have been fixed in the current version.

Current exposure: none, and that is worth stating precisely

A fresh install of the published package audits clean. Our range is glob: ^10.3.10,
which resolves [email protected] and [email protected] — both patched. Verified
by installing the package from the registry into an empty project:
found 0 vulnerabilities.

So this is not an open vulnerability. It is an abandoned dependency, which is a
different and slower problem: the next advisory in that line will not be patched.

Why the upgrade is not a patch release

glob latest 13.x
its engines 18 || 20 || >=22
our engines >=16.0.0

Upgrading drops Node 16, which makes it a breaking change to engines — semver-major,
so 8.0.0. Node 16 reached end of life in September 2023 and Node 18 in April 2025, so
requiring 18+ is defensible on its own merits; it is still not something to slip into a
patch.

Options

  1. Bump to glob 13 and require Node ≥18 in a 8.0.0 release. Honest, and clears the
    deprecation.
  2. Drop glob entirely. The dependency is used for file discovery; Node has had a
    native fs.glob since 22, which is a heavier engine requirement, not a lighter one.
    Worth measuring how much of glob we actually use before assuming this is simpler.
  3. Stay. Defensible only while the resolved transitive versions remain patched, and
    it silently accepts that they may not be.

No decision yet. Recording it here rather than leaving it in a chat log, because the
deprecation notice is visible to anyone auditing our supply chain and deserves a public
answer.

Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
38 min
PR fusionados (30 d)
96

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 Rule-Of-Code/RoC

Todos los issues de Rule-Of-Code/RoC

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.