glob@10 is deprecated upstream; upgrading requires dropping Node 16
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
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
- Bump to glob 13 and require Node ≥18 in a
8.0.0release. Honest, and clears the
deprecation. - Drop
globentirely. The dependency is used for file discovery; Node has had a
nativefs.globsince 22, which is a heavier engine requirement, not a lighter one.
Worth measuring how much ofglobwe actually use before assuming this is simpler. - 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Rule-Of-Code/RoC
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Rule-Of-Code/RoC#436 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Rule-Of-Code/RoC#439 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 49/100
Rule-Of-Code/RoC#438 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 53/100
Rule-Of-Code/RoC#437 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 74/100
Rule-Of-Code/RoC#435 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Rule-Of-Code/RoC
Issues similares
-
documentation lens:human needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
thebristolsound/birdbrain#2246 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
A voting window past about 69.9 million hours stores a deadline that reads back as no deadlineAbiertobug ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
BoardGamesEmpire/board-games-empire-backend#1452 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
good first issue stretch
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día